Which versions of kraken-trader are malicious?

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

How do I remediate kraken-trader if I installed it?

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

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

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

Malicious package

kraken-traderPyPI

Malicious code in kraken-trader (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-2517

Immediate action

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

pip uninstall kraken-trader

What this malware does

The package is a loader of malicious code disguised as remote "credits" code. The remote location, built from the parts in the code, delivers highly obfuscated JavaScript code that could be executed by the node.js runner embeded in the package. While all parts are in the package, it lacks the triggering code. As per Socket.dev attribution, it's a dependency used in North Korean fake interviews campaign.

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

Campaign: 2026-04-kraken-trader

Reasons (based on the campaign):

crypto-related
Downloads and executes a remote malicious script.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

4bf5ec6e8a6020de1e122cf07f2dde0f02fa1a484ff984586db379729da75523

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 kraken-trader (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kraken-trader across your stack and pipelines.
If you installed it — respond
kraken-trader 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 kraken-trader 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 kraken-trader 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. kraken-trader 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-kraken-trader

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks kraken-trader-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