Malicious code in sourceflow-tracker (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-5166
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (0c32024f2d571ac850d0e9a7240951137c14d1f1529ab3e0f782ff677a5625ea) 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. ## Source: ghsa-malware (02f647beb5bb5cf63b7b836740cc6de000c9a007627f1e013aec42ac359f6f29) 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. ## Source: ossf-package-analysis (1699207dcb748d9894d27585d5e49f48e906eae167d75434c15cd15f1aeb5502) 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.
- Source published
- 2 Jun 2026 11:40:44 UTC
- Source modified
- 13 Aug 2026 22:15:20 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.