eacq-acq-menunpm
eacq-acq-menu is a confirmed malicious npm package (MAL-2026-13205) that executes malicious code on install (malicious version 35.2.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in eacq-acq-menu (npm)
What this malware does
On require() of the package, index.js loads adapter.js which unconditionally executes a setup routine that fetches a platform-specific binary from runtime-reconstructed hosts (Cloudflare workers.dev subdomains such as oob-worker.cf10x-baf.workers.dev and *.dl.wel1.ru domains including sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), writes it to /tmp or %TEMP% under cover-story filenames (.cache<hex>, dotnet_diag_<hex>.exe), chmods it 0755, and spawns it detached via spawn("/bin/sh") or spawn("cmd"). Destination hostnames are assembled by.join("") of split substrings to defeat static string scanning, and a dnsChunked() routine reassembles a base64 payload from numbered TXT DNS records (c.<domain>, 0.<domain>, 1.<domain>,...) as a fallback delivery channel. The package advertises itself as a menu-provider library and performs no such function; the only observable effect of installing/importing it is delivery and execution of an opaque remote binary on the installer's host.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eacq-acq-menu (version 35.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eacq-acq-menu across your stack and pipelines.
If you installed it — respond
Remove eacq-acq-menu 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 eacq-acq-menu 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 eacq-acq-menu 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks eacq-acq-menu-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.