array-node-utilsnpm
Advisory published Updated
array-node-utils is a confirmed malicious npm package (MAL-2026-11130) that executes malicious code on install (malicious version 1.0.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in array-node-utils (npm)
What this malware does
The package's main file index.js is a heavily obfuscated (obfuscator.io RC4+base64 string-array) module whose top-level IIFE runs on require(). It loads https, path, os, fs, child_process, and crypto; assembles a 4-octet host string via repeated.concat calls to hide the destination; issues an https GET; pipes the response through crypto.createDecipheriv (AES) with a sha256-derived key; writes the decrypted bytes to a file under os.tmpdir(); and executes that file via child_process with windowsHide and cwd set to the user's home directory. The package's declared purpose ('array-node-utils') has no relationship to the shipped code — the module contains no array-handling logic, only the fetch-decrypt-exec chain.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for array-node-utils (version 1.0.9).
If you installed it — respond
Remove array-node-utils 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 array-node-utils 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks array-node-utils-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.