npm package report

Is tensorlake safe?

The malicious-package record for tensorlake covers every version, but the registry still serves 114 releases and the record does not name which were malicious. Check the references below before installing any version.

Malicious-package record: every version

CRITICAL

Malicious-package record. Added to CyberXYZ 2026-10-08, OSV malicious-package feed (Google / OpenSSF).

// what we observed

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Reported by GitHub Advisory Database via OSV.

// versions and what to do

Malicious: all versions

If one of these versions was installed, remove it and treat the credentials, tokens and SSH keys on that machine as exposed: rotate them. Check CI runners and container images that installed it too.

OSV record advisory

// reach

1 direct dependencies

none carry a known advisory

0 packages depend on it

an advisory here reaches each of them

Create a free accountfor every dependency path, dependent and what to upgrade

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-10-31 at 00:02 UTC. Updated continuously from NVD, GHSA, OSV and CNA feeds.