Which versions of krakenvirus are malicious?

The following PyPI versions of krakenvirus are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate krakenvirus if I installed it?

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

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

Yes — krakenvirus is associated with the RLMA-2025-04785, 2025-08-kraken-virus, RLUA-2026-00459 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 krakenvirus 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 krakenvirus (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging krakenvirus across your stack and pipelines.

Malicious package

krakenvirusPyPI

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

MAL-2025-47781

Immediate action

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

pip uninstall krakenvirus

What this malware does

As even described, the package contains a malicious code collecting large amount of data. The description suggests educational use, yet, the code can cause real harm. Specifically, the C2 servers defined in the package seems to be selected as trusted domains that would ignore the data sent. However, among them is at least one domain available for sale at the time of analysis - opening the room for collecting data by the uploader.

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

Campaign: 2025-08-kraken-virus

Reasons (based on the campaign):

malware
exfiltration-browser-data
exfiltration-generic

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

235feda43701777d7cc0575bbbc4730a4ebeb5a229c2cee23ade88e2a389b6d3

4207d583c3da548536f0ab0bc0660275f4839702841b1485effe9f8b87b3559d

be8d805ccb8e7b1ab32ad3a831ff1de9fae755190610c88fed7e0460aee1349e

ad20b613b8c371cc08df1d6c0925cfbf0b744ca0c454247101d7712927e7b040

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

Campaign

RLMA-2025-047852025-08-kraken-virusRLUA-2026-00459

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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