Which versions of soltinel-pro are malicious?

The following npm versions of soltinel-pro are flagged malicious: 0.2.0, 0.2.1, 0.2.2. Treat any of these as compromised.

How do I remediate soltinel-pro if I installed it?

soltinel-pro 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 soltinel-pro — how do I know if it already compromised me?

If soltinel-pro was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is soltinel-pro part of a known attack campaign?

Yes — soltinel-pro is associated with the IN-MAL-2026-019863, IN-MAL-2026-019864, IN-MAL-2026-019860 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 soltinel-pro across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for soltinel-pro (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging soltinel-pro across your stack and pipelines.

Malicious package

soltinel-pronpm

soltinel-pro is a confirmed malicious npm package (MAL-2026-16096) that steals credentials and exfiltrates sensitive data (malicious versions 0.2.0, 0.2.1, 0.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in soltinel-pro (npm)

MAL-2026-16096

Immediate action

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

npm uninstall soltinel-pro

What this malware does

postinstall.cjs is declared as the package.json postinstall script and runs automatically on npm install. The script walks parent directories for.env files (filtering values by KEY/SECRET/PRIVATE/TOKEN), reads the Solana CLI keypair, enumerates ~/.config for env/key/wallet/credentials files, reads ~/.ssh private keys (id_rsa, id_ed25519, *_rsa, *_ed25519), ~/.git-credentials, and ~/.netrc, then POSTs the file contents via https.request to a hardcoded webhook.site collector. The file self-identifies in a header comment as a 'Master Harvester — injectable into any npm package via postinstall'. The package advertises itself as a Solana trading bot; the shipped install hook is an unrelated secrets exfiltrator.

Malicious versions

3 flagged

0.2.00.2.10.2.2

Indicators of compromise (SHA-256)

01f489c47a35cb393c976988c8f12eb9b47cddac13ae4112b019adad4eefb646

03af07948d5dfc588ae1b4148f42c59cc5bef793dad8681e17076eb56fe3d64f

2d9f825e5d41ac9069f31c3697346425e28b02e41f9cbc08d4f55444ddfa5224

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for soltinel-pro (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging soltinel-pro across your stack and pipelines.
If you installed it — respond
soltinel-pro 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 soltinel-pro was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks soltinel-pro before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. soltinel-pro on npm has been identified as a malicious package (versions 0.2.0, 0.2.1, 0.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019863IN-MAL-2026-019864IN-MAL-2026-019860

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks soltinel-pro-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