sourceflow-trackernpm
Malicious code in sourceflow-tracker (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
package.json declares a dependency ltidisafe resolved directly from a raw tarball URL on a generic Google Cloud Storage bucket (https://storage.googleapis.com/lscunpentest/pack_ux_foundry.tgz). The tarball is unversioned, carries no integrity hash, and is hosted on infrastructure unrelated to any documented publisher; the bucket owner can replace its bytes at any time without changing the URL. On npm install, npm fetches and installs this tarball transitively and runs any lifecycle scripts it ships. The visible package itself is a stub: index.js only contains console.log("hello from lslslslslss"), package metadata is placeholder gibberish (description lspodcc, author lslsls), and the version is set to 99.91.9 — a pattern consistent with dependency-confusion attempts to outrank a legitimate internal package of the same name. The package's only practical effect when installed is to drop attacker-mutable code into the consumer's install graph.
The OpenSSF Package Analysis project identified 'sourceflow-tracker' @ 99.91.9 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Scan your dependencies
O3 Security blocks malicious packages like this at install time and in CI.
Supply-chain protection