Which versions of solana-core-4 are malicious?

The following npm versions of solana-core-4 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate solana-core-4 if I installed it?

solana-core-4 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 solana-core-4 — how do I know if it already compromised me?

If solana-core-4 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 solana-core-4 part of a known attack campaign?

Yes — solana-core-4 is associated with the IN-MAL-2026-009488 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 solana-core-4 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for solana-core-4 (version 1.0.0).

Malicious package

solana-core-4npm

Advisory published Jun 9, 2026Updated Jul 9, 2026

solana-core-4 is a confirmed malicious npm package (MAL-2026-5358) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in solana-core-4 (npm)

MAL-2026-5358

Immediate action

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

npm uninstall solana-core-4

What this malware does

Crypto/SSH/wallet stealer, blockchain-helper-0/web3-tools-9 campaign sibling (c960/c961). postinstall scripts/postinstall.js auto-execs, src/index.js harvests ~/.ssh/id_rsa+wallet keys/seeds+env, self-labels "CRYPTO STEALER", exfils to IDENTICAL Telegram bot 8227918239 chat 6433587894 (not rotated). Generic-crypto-name + numeric suffix + 1.0.0 pattern.

The package was found to contain malicious code or consuming dependency that contains malicious code

The OpenSSF Package Analysis project identified 'solana-core-4' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

efb376d3542aadcfbbb9f689dcfcd73534f230fbe75ed465327444685097fd6d

61592bcace57b51c5e1371d9645f1a3ab04ea4d9e148dcacca192ed98e82e36c

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-009488

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder
SafeDep · finder

Detect & block this

O3 blocks solana-core-4-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