Which versions of kyjnzu are malicious?

The following npm versions of kyjnzu are flagged malicious: 4.2.3. Treat any of these as compromised.

How do I remediate kyjnzu if I installed it?

Remove kyjnzu 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.

I already installed kyjnzu — how do I know if it already compromised me?

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

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

Malicious package

kyjnzunpm

Malicious code in kyjnzu (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191577

Immediate action

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

npm uninstall kyjnzu

What this malware does

The package kyjnzu was found to contain malicious code.

Malicious versions

1 flagged

4.2.3

Indicators of compromise (SHA-256)

12b690dcafaba865d7e9b50332f5ae3d4393693d7ae12d62993b884e33796393

76ec5839e1ac972ae9271550bfe712c6d00f654ebce392fdc89762ab7347a663

f729ff2833952f9a5421d883e1998a5e916e171eb683c3d3750ab9c74f0eb7c9

1bd4f664347b99079d463f44d124c228eeef5ea21e51c5353fdd3638f184cb9d

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for kyjnzu (version 4.2.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kyjnzu across your stack and pipelines.
If you installed it — respond
Remove kyjnzu 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.
Did it already run?
If kyjnzu 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 kyjnzu 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. kyjnzu on npm has been identified as a malicious package (version 4.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05823RLUA-2025-06394RLUA-2026-01396

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks kyjnzu-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.

Malware detection Runtime egress monitoring