Trigger.dev customer environment variables exposed (trigger.dev)
87 points by anurag 9 hours ago
corvad 5 hours ago
I am sorry, this is "Resolved"? How can they even consider marking this resolved in any situation. Yeah we exposed your env vars but we told you about it over email so it's all good... We dont know how or to what extend though.
janpio 31 minutes ago
What would you consider appropriate action for their incident team to be able to mark the incident on their status page as resolved?
ygouzerh 11 minutes ago
Never put it resolved
theturtletalks 5 hours ago
The biggest case for building bespoke software is that you drop your attack surface area and it’s not as lucrative to hack one person. Don’t even expose it to the internet if you don’t need to and just run Tailscale.
pelagicAustral 28 minutes ago
Tailscale got hacked recently as well, didnt they (?). I think they did, the whole system is poisoned, because I believe one of the vectors had to do with eMudhra certs, which again, is not an issue specific to them, or something they had any say on it... there is literally no escape these days it would seem.
cbluth 3 hours ago
I think you've just explained why people rent infrastructure.
shepherdjerred 2 hours ago
This is probably correct if you aren’t a target at all, e.g. you aren’t running a business
iampims 6 hours ago
It’s bold to set status page incident to resolved.
weird-eye-issue 5 hours ago
If they fixed the exploit then what do you want them to do? Do they need to wait an arbitrary amount of time before setting it to resolved?
eddythompson80 5 hours ago
I don't disagree with you, but I think generally when the mistake involves compromised user data, the answer is a bit more emotionally driven. People get rightfully mad when things like that happens, and services usually keep the incident in a "Mitigated" status while they "work with their customers to ensure blah blah blah" or whatever. Everywhere I've personally worked the Mitigated->Resolved involves publishing a postmortem, repair items, and general assurances or safe guards based on learnings from the incident that the issue won't happen again. However, the industry as a whole doesn't have a standard for what the line between Mitigation and Resolution is.
weird-eye-issue 5 hours ago
rugma 3 hours ago
they could have explained a bit better with proper postmortem and steps taken to improve, before marking it as resolved
Traubenfuchs 2 hours ago
They are no longer exposing anything, so they no longer have an incident.
Their customers now have an incident that will be resolved once their secrets are rotated. Maybe they also need to do previous intrusion forensics… In any case, not triggers problem anymore.
cheeze 5 hours ago
I like the fancy gradient INCIDENT REPORT image as well. At least it looks fancy and AI-ey
BADCAFE 3 hours ago
This also happened to a trigger.dev competitor a few months ago, inngest.
I was able to patch before it was exploited but that definitely made me question the service.
reassess_blind 6 hours ago
Have any of these companies disclosed the actual vulnerabilities used to gain access to their systems?
dboreham 5 hours ago
No. Which may mean they don't know.
tough 2 hours ago
the recent CVE making any non-patched TCP exposed linux server RCE-root-able seems like a good stretch to me.
But could also be any of the recent supply chain attacks hitting a dev too i guess
asdfsa32 5 hours ago
So at this rate, how long before people start hiding use of AI in development of in their SaaS and services? or people really don't care, do they?
Kiro an hour ago
Hand-made code is riddled with dirty hacks and exploits that LLMs have no problem finding. I would not trust any software that is not using frontier models to fix the messy human code.
asdfsa32 an hour ago
Oh that is right, the frontier models yield amazing architecture and secure code in the form of aislop.
There is a difference between using AI to find bugs in written software than using AI to write bug free software, completely different set of skills and outcomes. Most of the high profile stuff you see is AI being driven by people who would have solved the same problem just in slower time going through the code. AI is as good as the operator.
fathermarz 5 hours ago
Holy smokes, is security just not a priority at all anymore? Like in what world do we live in, that this is acceptable. And at the volume this has been happening, bad guys are having a FIELD DAY.
OccamsMirror 4 hours ago
What makes you think security was ever a priority?
cpursley 4 hours ago
The very fact that Nextjs vibe projects need an external (and paid!) background jobs / async service show how much of an anti pattern that this framework and similar are. Just use a sensible stack from day one that can handle concurrency out of the box like Elixir or something with established open source background jobs library. Then you can worry less about this kind of paid 3rd party nonsense. Ditto on auth. I just can't fathom outsourcing these types or core functionalities, the operational, security and cost risks make very little sense when there's libraries that do this out of the box.
multiplegeorges 4 hours ago
Yes, outsourcing these kinds of core functionality (your queue, your users table!) is insane to me.
rvz 5 hours ago
Given the recent Claude Code remote access tool, it would be wise to not install any new software, or use any package manager for a few weeks as they could have already been silently backdoored during the aftermath of that incident.
tough 2 hours ago
I was paranoid enough to just remove all my Chrome/VSCode etc extensions.
Im now thinking about just running tart VM's on my mac to do my regular stuff from.