Malicious code in tostpro (npm)

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7785c0ac37ad4bb74abc644be2a5fc48bdb0d1248027e607fdf13ddaaa59d546) Package [email protected] declares scripts.preinstall='sh./rce_poc.sh'. On install, the shipped shell script runs id/hostname/pwd and appends a timestamped line to./RCE_POC_MARKER.txt in the installer's working directory. The script performs no network I/O, reads no credentials or environment, writes nothing outside the install tree, and installs no persistence. The declared main entry dist/index.js is not shipped in the tarball, so the package has no library/import-time behavior; the preinstall marker write is its only effect. The README identifies the package as a security-research canary demonstrating dependency-confusion exposure for an internal name, consistent with the implausibly high version (99.101.0) used to win resolution against an internal package. The preinstall execution path is a real supply-chain concern in principle because a future version could replace the benign marker with a hostile payload, but this version's shipped payload produces no attacker benefit and no destructive action against the installer. ## Source: ghsa-malware (95a0ca1794b466d8ca8d84b64429987b6683b2b316794f522dc160bf35bce216) 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 published

5 Oct 2026 03:34:20 UTC

Source modified

25 Oct 2026 15:30:04 UTC

Observed here

25 Oct 2026 16:17:16 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.