Skip to content
~/pwn.watch_

Get notified

Get an email when a new major security incident drops. No spam, unsubscribe any time.

Only used for pwn.watch incident emails. Protected by Cloudflare Turnstile.

Become a sponsor

One slot: pwn.watch, gifs.so, flavors.design, kitze.io, every kitze repo, and an X shout-out.

YearlyBest value · save 44%$999/year$83.25/mo, billed yearly. Save $789 vs monthly (5+ months free).Monthly$149/monthBilled monthly. Cancel anytime.

Secure checkout on Polar. Right after paying you set up your ad on kitze.io.

Tensorlake

Security incidents tagged Tensorlake. Newest first.

1 Tensorlake incident in the last 12 months

Critical 4 · High 3 · Med 2 · Low 1 · Update ½LessMore
Incidents
1
Live
1
Patched
0
Days without an incident
0
Longest quiet run: 0 days
All tags →

Brought to you byTinkerer Club

The private club for people who own their servers, run their own AI, and pay $0/month for software.

  • HighPartly patched

    Tensorlake: attacker reached engineering GitHub via vendor-hosted sandboxes after unrotated env vars

    On Nov 8 2026 Tensorlake founder Diptanu Choudhury disclosed a security incident. He said an application running on an upstream provider spun up sandboxes in Tensorlake engineering-team accounts that had access to the company’s GitHub repositories; an attacker pushed malicious code to branches and triggered GitHub Actions to probe for secrets those workflows can access. The first published version of the post named the provider as Railway; later edits of the same post say “an upstream provider” and add that the provider had a security breach a couple of weeks earlier that exposed environment variables, that Tensorlake had not rotated those env vars because the application was not critical for production, and that this was an oversight. He said there was no impact to customer information such as API keys or sandboxes, that Tensorlake has no evidence any critical systems were accessed beyond probing for secrets, that it has rotated all secrets and undeployed the internal application, and that paying customers have been notified by email. Out of abundant caution he asked customers to rotate Tensorlake API keys. Further details are promised by email and on Tensorlake’s trust center. This is separate from the October 2026 tensorlake npm Shai-Hulud worm.

    Tensorlake (AI sandbox platform)Since Nov 8, 2026

Posts 1

  • Tensorlake: attacker reached engineering GitHub via vendor-hosted sandboxes after unrotated env vars
    Diptanu Choudhury
    @diptanu

    We had a security incident on Tensorlake today. There was no impact to customer information such as API keys or sandboxes. An application running on an upstream provider spins up sandboxes in our engineering team’s accounts and runs automation workflows. These sandboxes had access to our GitHub repositories. The attacker pushed malicious code to branches and triggered GitHub Actions to probe for secrets that workflows can access to build and deploy code. The upstream provider had a security breach a couple of weeks ago that exposed our environment variables. We had not rotated those env vars, as this is not a critical application for our production environment. This was an oversight, we should have acted on this immediately. We have no evidence that any critical systems were accessed beyond probing for secrets. We have rotated all secrets and undeployed the internal application from the upstream provider. Out of abundant caution, please rotate your Tensorlake API keys. We will share more information with customers over email and post updates in our trust center. We have already notified all paying customers by email, and we will follow up with additional details.

Sponsored

Buy sponsor slot · $149/mo