Which versions of prediction-trader are malicious?

The following npm versions of prediction-trader are flagged malicious: 2.3.0. Treat any of these as compromised.

How do I remediate prediction-trader if I installed it?

prediction-trader 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.

I already installed prediction-trader — how do I know if it already compromised me?

If prediction-trader 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.

Is prediction-trader part of a known attack campaign?

Yes — prediction-trader is associated with the IN-MAL-2026-017658 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find prediction-trader across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for prediction-trader (version 2.3.0).

Malicious package

prediction-tradernpm

Advisory published Aug 13, 2026Updated Aug 13, 2026

prediction-trader is a confirmed malicious npm package (MAL-2026-13959) that steals credentials and exfiltrates sensitive data (malicious version 2.3.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in prediction-trader (npm)

MAL-2026-13959

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall prediction-trader

What this malware does

index.js contacts a hardcoded bare-IP endpoint at 31.97.137.157:45000/icons/108 disguised as an icon/CDN fetch (variables named iconDomain/getPlugin, path /icons/, header 'bearrtoken: logo'), retrieves a JSON response, and passes the response's credits field into new Function('require','module',...,data.credits) invoked with full Node capabilities (require, module, process, Buffer, globals). Any consumer that loads the package and invokes the default export executes arbitrary attacker-controlled JavaScript delivered from that endpoint. The cover-story naming (unused setDefaultModule referencing cdnjs/cloudflare decoy domains) conflicts with the README's benign trading-library description. The declared dependencies (node-machine-id, @primno/dpapi, better-sqlite3) are consistent with wallet and browser-cookie stealer tooling and provide primitives the remotely fetched code can leverage.

Malicious versions

1 flagged

2.3.0

Indicators of compromise (SHA-256)

da26a91c3cc6d5bf4957fa3f713a63e579b820c40b57b24209df61b2a53d7e87

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for prediction-trader (version 2.3.0).
If you installed it — respond
prediction-trader 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 prediction-trader 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. prediction-trader on npm has been identified as a malicious package (version 2.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017658

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks prediction-trader-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database