Which versions of node-cache-multithread are malicious?

The following npm versions of node-cache-multithread are flagged malicious: 1.1.3. Treat any of these as compromised.

How do I remediate node-cache-multithread if I installed it?

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

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

Yes — node-cache-multithread is associated with the IN-MAL-2026-014877 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 node-cache-multithread 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 node-cache-multithread (version 1.1.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-cache-multithread across your stack and pipelines.

Malicious package

node-cache-multithreadnpm

node-cache-multithread is a confirmed malicious npm package (MAL-2026-12403) that executes malicious code on install (malicious version 1.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-cache-multithread (npm)

MAL-2026-12403

Immediate action

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

npm uninstall node-cache-multithread

What this malware does

index.js, the package's declared main entry, is a ~23KB obfuscator.io RC4/base64 string-array bundle whose top-level IIFE runs on require(). It requires fs, os, path, child_process, and an HTTP client; builds a hardcoded remote URL from four numeric octets and a port (concealed inside the 314-entry string array); fetches a payload; splits the response into IV and ciphertext on ':'; decrypts with a hardcoded key via crypto.createDecipheriv; writes the plaintext to a file under os.tmpdir(); and spawns/execs it through child_process with windowsHide:true. The package advertises itself in the README as @array-util/nodepull while publishing under the name node-cache-multithread, so a developer following the README will install/require a differently-named tarball whose only shipped file is the dropper. No cache/library functionality is present.

Malicious versions

1 flagged

1.1.3

Indicators of compromise (SHA-256)

09be7b43b4fe5e0c786fb116e4a99518c46825e2b18b5e65eca88c51470b07a0

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 node-cache-multithread (version 1.1.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-cache-multithread across your stack and pipelines.
If you installed it — respond
Remove node-cache-multithread 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 node-cache-multithread 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 node-cache-multithread 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. node-cache-multithread on npm has been identified as a malicious package (version 1.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014877

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks node-cache-multithread-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