Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@array-util/nodepullnpm

@array-util/nodepull is a confirmed malicious npm package (MAL-2026-6084) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @array-util/nodepull (npm)

MAL-2026-6084
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @array-util/nodepull

What this malware does

@array-util/[email protected] ships a single 19 KB obfuscated index.js as its main entry. On require()/import, the IIFE silences process error handlers via process.on('uncaughtException',...) and process.on('unhandledRejection',...), builds a URL by chained string.replace() calls to reassemble dotted host/path tokens, loads os/fs/path/child_process plus an HTTP client, downloads a remote resource, writes the response body to path.join(os.tmpdir(), <name>) with flag 'w+', and executes the dropped file via child_process.exec with {windowsHide: true, cwd: process.cwd()}. The string array, decoder (custom-base64 + RC4 via function c(b,d)), and control-flow flattening (obfuscator.io output, ~814 transforms per webcrack) conceal the URL, dropped filename, and exec target so URL/IP pattern scanners cannot read them. Package metadata is hollow (empty description, empty author, ISC license, no documented API; README only shows an install line and a bare require()) — there is no legitimate functionality, only the dropper. Any developer or build system that installs and require()s this package fetches and executes attacker-controlled code under the installer's UID with errors silenced.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

9 flagged
1.0.01.0.11.0.21.0.31.0.41.1.01.1.11.1.21.1.3

Indicators of compromise (SHA-256)

bcafb3a6336948fd12673cfe88d505e2a036afcfb5e9ee5d4b850cf982753d9b
c171d764fc1dd7e67c3a09b1092c94ae915786d3776a1246c916f153095a92cb
e5a36af206cdff9358c1d3357469fd896fb1607d2401b6f035aaaf35451babac
f15b273b560a498837df1f05f8525771f4432eb32abb85f2f0560196531f034d
0aeb6128007cbaa191cb28519e1204c2d9d086088604c3bfcdf8dfb95c2b0414
5c68e8de606d68841b0681a7dda1a084dd0c322f05c49f2ac5334da21d1bbea1
a3e16211698fe696cd440a228d27b379591927c7391c755217dd64b41d972f82
a9bb4d88f84c066cc15071e6202634acd3544a002f77af442a9eb4c5088b711d
e22512181fe999a74644d09611426c577e7391f15e75f5ecbeacd7f2bdcb1ff1
f39ee2115316e7a4ef61c29a6597291e41486941fae87be5a8a2fb2a10f78e67

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @array-util/nodepull (9 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @array-util/nodepull across your stack and pipelines.

  2. If you installed it — respond

    @array-util/nodepull is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @array-util/nodepull 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.

  4. How O3 protects you

    O3 blocks @array-util/nodepull 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. @array-util/nodepull on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.1.0, 1.1.1, 1.1.2, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006946IN-MAL-2026-006947IN-MAL-2026-006948GHSA-qhxp-5mv2-773fIN-MAL-2026-013011IN-MAL-2026-013007IN-MAL-2026-013268IN-MAL-2026-013267IN-MAL-2026-012959IN-MAL-2026-012963

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @array-util/nodepull-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@array-util/nodepull (npm) malicious package — MAL-2026-6084 | O3 Security