Which versions of eacq-acq-menu are malicious?

The following npm versions of eacq-acq-menu are flagged malicious: 35.2.1. Treat any of these as compromised.

How do I remediate eacq-acq-menu if I installed it?

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.

I already installed eacq-acq-menu — how do I know if it already compromised me?

If eacq-acq-menu 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 eacq-acq-menu part of a known attack campaign?

Yes — eacq-acq-menu is associated with the IN-MAL-2026-015581 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 eacq-acq-menu across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for eacq-acq-menu (version 35.2.1).

Malicious package

eacq-acq-menunpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

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)

MAL-2026-13205

Immediate action

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

npm uninstall eacq-acq-menu

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

1 flagged

35.2.1

Indicators of compromise (SHA-256)

ae7929c06f789a6fc910fd4ce4697fd5d32f06b55a0c9b5e406110f90676c239

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for eacq-acq-menu (version 35.2.1).
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 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. eacq-acq-menu on npm has been identified as a malicious package (version 35.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015581

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database