<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <title>trigger.dev</title>
  <subtitle>Browse aymeric&#39;s, an independent, searchable archive of readable snapshots from followed feeds, preserved in Git with aggr.</subtitle>
  <id>https://aggr.aymericbeaumet.com/sources/trigger.dev/</id>
  <link rel="alternate" type="text/html" href="https://aggr.aymericbeaumet.com/sources/trigger.dev/"/>
  <link rel="self" type="application/atom+xml" href="https://aggr.aymericbeaumet.com/sources/trigger.dev/atom.xml"/>
  <updated>2026-11-02T01:09:16+00:00</updated>
  <author>
    <name>aymeric&#39;s</name>
  </author>
  <generator version="2.0.0" uri="https://github.com/aymericbeaumet/aggr">aggr</generator>
  <entry>
    <id>urn:aggr:item:4e6228cc5cbc3cbdaadad9dbec4bb7afe877333b</id>
    <title type="text">Trigger.dev customer environment variables exposed</title>
    <link rel="alternate" type="text/html" href="https://aggr.aymericbeaumet.com/items/hnrss-org/2026-11-02-trigger-dev-customer-environment-variables-exposed/"/>
    <link rel="via" type="text/html" href="https://trigger.dev/blog/security-incident-nov-2026"/>
    <published>2026-11-02T01:09:16+00:00</published>
    <updated>2026-11-02T01:09:16+00:00</updated>
    <author>
      <name>anurag</name>
    </author>
    <category term="news"/>
    <source>
      <title>Hacker News: Front Page</title>
    </source>
    <summary type="text">Incident report · November 1, 2026 View all blog posts Eric Allam CTO, Trigger.dev There has been a security incident at Trigger.dev. We&#39;ve blocked the exploit used in this attack, but our investigation has identified exposure across a…</summary>
    <content type="html">&lt;p&gt;&lt;a target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot; href=&quot;https://trigger.dev/blog&quot;&gt;Incident report · November 1, 2026 View all blog posts&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot; href=&quot;https://x.com/maverickdotdev&quot;&gt;&lt;picture class=&quot;article-picture article-picture-fallback&quot; style=&quot;--image-ratio:16 / 9&quot;&gt;&lt;img src=&quot;https://trigger.dev/blog/authors/eric.png&quot; alt=&quot;Eric Allam&quot; loading=&quot;eager&quot; decoding=&quot;async&quot; fetchpriority=&quot;high&quot; referrerpolicy=&quot;no-referrer&quot; class=&quot;progressive-image&quot;&gt;&lt;/picture&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot; href=&quot;https://x.com/maverickdotdev&quot;&gt;Eric Allam&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;CTO, Trigger.dev&lt;/p&gt;
&lt;p&gt;&lt;picture class=&quot;article-picture article-picture-fallback&quot; style=&quot;--image-ratio:16 / 9&quot;&gt;&lt;img src=&quot;https://trigger.dev/blog/generic/incident-report-generic.png&quot; alt=&quot;Image for Security Disclosure: Sunday November 1st&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; fetchpriority=&quot;low&quot; referrerpolicy=&quot;no-referrer&quot; class=&quot;progressive-image&quot;&gt;&lt;/picture&gt;&lt;/p&gt;
&lt;p&gt;There has been a security incident at Trigger.dev.&lt;/p&gt;
&lt;p&gt;We&#39;ve blocked the exploit used in this attack, but our investigation has identified exposure across a subset of organizations.&lt;/p&gt;
&lt;p&gt;The attacker gained unauthorized access to environment variables for these organizations.&lt;/p&gt;
&lt;p&gt;We have emailed all impacted account owners with steps to mitigate.&lt;/p&gt;
&lt;p&gt;We will publish updates on our &lt;a target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot; href=&quot;https://status.trigger.dev/incident/1110434?mp=true&quot;&gt;status page&lt;/a&gt;, and you can &lt;a target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot; href=&quot;https://trigger.dev/contact&quot;&gt;contact us&lt;/a&gt; if you have any questions.&lt;/p&gt;
</content>
  </entry>
</feed>
