• Sources: primary, issue, discussion
  • Summary: StepSecurity names tensorlake 0.5.144 as the malicious release, 0.5.143 as the pin, and tensorlakeai/tensorlake main commits e90c47b to 6386121 as the compromised range. The release was built from the project's own main branch and carries a valid npm provenance attestation, and StepSecurity found 0.5.144 still downloadable from npm when it checked. The package steals a GitHub token and installs a background service that deletes the user home directory once the token stops working, so the published remediation order is to remove ~/.config/gh-token-monitor first and rotate credentials afterwards.
  • Why it matters: Revoking the stolen GitHub token first triggers the background service that runs rm -rf on the user home directory, so the standard first step of incident response is what causes the damage, and a valid provenance attestation on a build from the project's own main branch defeats a provenance-trust policy.
  • Follow-up: Whether 0.5.144 is removed from the registry, and what the project publishes on scope.