Technology

provenance attestations

1 synchronized story carry this tag.

Malicious Tensorlake package turns token revocation into a wipe trigger

StepSecurity reported that tensorlake 0.5.144 on npm stole developer credentials, attempted to spread through packages and repositories, and installed a token monitor that deletes the user's home directory if the stolen GitHub token is revoked. The package was built from the compromised upstream main branch and carried npm provenance.

Why it matters: The incident shows why provenance proves build origin, not code safety, and why routine token revocation can be destructive when malware monitors credential validity. It also used Claude and VS Code project configuration as persistence and propagation paths.

Read storyOriginal source · stepsecurity.io