Which versions of nokaca are malicious?

The following npm versions of nokaca are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate nokaca if I installed it?

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

If nokaca was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is nokaca part of a known attack campaign?

Yes — nokaca is associated with the RLMA-2025-06436 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 nokaca across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nokaca (2 malicious versions).

Malicious package

nokacanpm

Advisory published Dec 23, 2025Updated Jan 2, 2026

nokaca is a confirmed malicious npm package (MAL-2025-192848) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nokaca (npm)

MAL-2025-192848

Immediate action

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

npm uninstall nokaca

What this malware does

The package nokaca was found to contain malicious code.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

f5ca7b087b4131f575d624859cfdbf8c8a90d43c0692f5bf014df3e7d84a0f68

b58137bd28db53bb19b475195c6e7d9b64cd589437c73116ca96f400daf7b223

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for nokaca (2 malicious versions).
If you installed it — respond
Remove nokaca 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 nokaca was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. nokaca on npm 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

RLMA-2025-06436

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database