StepSecurity: Tensorlake npm compromise and provenance failure

Evidence record

Forensic description of malicious commits, npm release 0.5.144, valid build provenance, install-time credential collection, agent configuration poisoning and a destructive token-revocation trap.

Read the original source ↗

Claim-level citations (3)

• supportsA compromised Tensorlake release used valid npm provenance to deliver a credential-stealing worm: StepSecurity found a background GitHub-token monitor designed to remove user files after token revocation, making remediation order a material risk for affected installations.

  The Hostage Token; Remediation

• supportsA compromised Tensorlake release used valid npm provenance to deliver a credential-stealing worm: StepSecurity linked tensorlake@0.5.144 to malicious October 7 commits placed on the real main branch and published October 8 by the legitimate release workflow with valid npm provenance.

  Executive summary; What happened; Impacted versions

• supportsA compromised Tensorlake release used valid npm provenance to deliver a credential-stealing worm: The analyzed package targeted developer credentials and planted .claude/settings.json and .vscode/tasks.json in reachable repositories to trigger execution through AI coding or editor workflows.

  Executive summary; What it steals; How it spreads