Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

kraken-uinpm

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

MAL-2026-5399
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall kraken-ui

What this malware does

On require/load, index.js imports os, dns, https, querystring, and the local package.json, then collects os.hostname(), os.userInfo().username, os.homedir(), __dirname (install path), dns.getServers(), and the full package.json contents, and HTTPS POSTs the JSON payload to nlc574f24tq03k423v3jr7hllcr3ft3i.oastify.com (a Burp Collaborator OAST subdomain). The version 999.0.0 plus self-described 'dependency confusion proof of concept' is the canonical dependency-confusion attack shape: it is published to the public registry to override an internal package of the same name. Any installer or build system whose resolver picks up this version leaks identifying host/user info and internal DNS topology to an attacker-controlled out-of-band server. Behavior fires automatically when the module's main entry is loaded.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
999.0.0

Indicators of compromise (SHA-256)

168f5bafda658807ea431a8cb06a1e3006d639d17b7f0c97d3d63e34f49129d5
88479e71edbc32519f47f7b8dc147285016c90e64650c763a784fee83f022c95
ea308da371652779c24ee15abd8d68c0908ea822dacf5599758c113b8a7ed13c
70dce5996cf028f13447c46cd3b825ad89f4580b1e02f7f2ae99a8b76d23275b

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for kraken-ui (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kraken-ui across your stack and pipelines.

  2. If you installed it — respond

    Remove kraken-ui from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If kraken-ui 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.

  4. How O3 protects you

    O3 blocks kraken-ui 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-ui on npm has been identified as a malicious package (version 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004965IN-MAL-2026-004966GHSA-g324-m33p-jjf4RLMA-2026-05566

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks kraken-ui-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

kraken-ui (npm) malicious package — MAL-2026-5399 | O3 Security