Which versions of node-array-plus are malicious?

The following npm versions of node-array-plus are flagged malicious: 1.0.9, 1.1.9. Treat any of these as compromised.

How do I remediate node-array-plus if I installed it?

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

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

Yes — node-array-plus is associated with the IN-MAL-2026-010911, IN-MAL-2026-014870 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-array-plus across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for node-array-plus (2 malicious versions).

Malicious package

node-array-plusnpm

Advisory published Jul 28, 2026Updated Aug 5, 2026

node-array-plus is a confirmed malicious npm package (MAL-2026-11142) that executes malicious code on install (malicious versions 1.0.9, 1.1.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-array-plus (npm)

MAL-2026-11142

Immediate action

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

npm uninstall node-array-plus

What this malware does

index.js is heavily obfuscated with a 312-entry rotated string array plus RC4/base64 decoders that hide identifiers and literals. On require(), the module builds a hardcoded IPv4 endpoint by concatenating four numeric octets, performs an HTTP GET against that endpoint, AES-256-CBC-decrypts the response using an MD5-derived key with an IV taken from the response, writes the plaintext to a file under os.homedir(), and executes it via child_process with windowsHide:true and cwd=os.homedir(). The package exposes no legitimate API surface (empty description, no exported functionality) — its sole effect on import is to drop and run remote code on the installer's machine. Obfuscation is used specifically to conceal the destination and the decrypt-drop-exec chain.

Malicious versions

2 flagged

1.0.91.1.9

Indicators of compromise (SHA-256)

e1ce58719e0587902be3a6436f329ce631317fe3a7c322d89f9c679cd6e1a744

40b0c2825705c60185bb3391c58ace7356e4f363483574bca9eb5d6e7c3a0f52

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for node-array-plus (2 malicious versions).
If you installed it — respond
Remove node-array-plus 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-array-plus 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. node-array-plus on npm has been identified as a malicious package (versions 1.0.9, 1.1.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010911IN-MAL-2026-014870

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks node-array-plus-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