Which versions of solanakit are malicious?

The following PyPI versions of solanakit are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate solanakit if I installed it?

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

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

Yes — solanakit is associated with the 2026-04-genosys 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 solanakit 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 solanakit (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging solanakit across your stack and pipelines.

Malicious package

solanakitPyPI

Malicious code in solanakit (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-2837

Immediate action

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

pip uninstall solanakit

What this malware does

During import, the code downloads and starts a malicious package hosted on GitHub. It then first ensures persistency e.g., through the autostart registry key. Then, based on the encrypted config, an exfiltration demon is started. It registeres the instance in the C2 server and starts searching the file system looking for files matching given filename patterns and then monitoring changes. Discovered files are exfiltrated to hardcoded remote target. The PyPI packages are used as dependencies in newly-created crypto-related repositories on GitHub.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-04-genosys

Reasons (based on the campaign):

files-exfiltration
peristence-autorun
obfuscation
The malicious code is intentionally included in a dependency of the package
exfiltration-credentials
persistence
crypto-related

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

3e8770458eab636335241e359b6cee149cc00640fb2418b4462c89ec88accc93

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 solanakit (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging solanakit across your stack and pipelines.
If you installed it — respond
solanakit 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 solanakit 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 solanakit 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. solanakit on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-04-genosys

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks solanakit-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