Which versions of kraken123 are malicious?

The following PyPI versions of kraken123 are flagged malicious: 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.5.0. Treat any of these as compromised.

How do I remediate kraken123 if I installed it?

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

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

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

Malicious package

kraken123PyPI

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

MAL-2025-191778

Immediate action

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

pip uninstall kraken123

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

5 flagged

0.1.00.2.00.3.00.4.00.5.0

Indicators of compromise (SHA-256)

36e96c988702835bbe57867c03f8066e0013c4ba0387b75a40240be6053cee9a

dc2f76a61af953726f4fc219f725013ce8b477860b47433b7fc0444994ffcfd5

743144de203d6ca5d29a26cc27d8ebbde60e11e94756cc327b3fc92e8bba2495

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

Campaign

2025-08-kraken-virus

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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