Trigger.dev customer environment variables exposed
0 comments
- Points145
- Comments72
0 comments
Story details from Hacker News ↗ · linked article on trigger.dev.
Trigger.dev customer environment variables exposed was first seen on Hacker News · Front page on Nov 2, 2026. Since then it has appeared in 62 checks on 1 different day. Its best position was #10 of 30, reached on Nov 2, 17:37 UTC. It dropped off the list after Nov 2, 18:37 UTC.
Position on Hacker News · Front page at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Hacker News.
A few top-level comments from Hacker News, shortened. Read the full thread on Hacker News.
As I mentioned in the Northflank breach post: Unfortunately for infra startups, I think we're going to see a convergence back to hyperscalers as a result of incidents like this and railway. There's no amount of "nicer to use" that can replace security, at least certainly when selling to enterprises Also, a trick i've…
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.
As far as my personal life is concerned, I honestly don't think I'm going to 'build and deploy' anything to any SaaS that isn't directly in my control for a while.
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 2, 18:37 UTC, after 1 day of trending.
#10 on Hacker News · Front page, on Nov 2, 17:37 UTC. Trendoday checks this list every 15 minutes.
It was first seen on Nov 2, 2026 and has been on the list on 1 day (62 checks) since.
145 points and 72 comments; submitted by anurag on Nov 2, 2026.