Which versions of eacq-dialog are malicious?

The following npm versions of eacq-dialog are flagged malicious: 35.8.1. Treat any of these as compromised.

How do I remediate eacq-dialog if I installed it?

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

If eacq-dialog 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.

Is eacq-dialog part of a known attack campaign?

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

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

Malicious package

eacq-dialognpm

eacq-dialog is a confirmed malicious npm package (MAL-2026-13515) that executes malicious code on install (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eacq-dialog (npm)

MAL-2026-13515

Immediate action

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

npm uninstall eacq-dialog

What this malware does

[email protected] contains a dropper reachable both from setup.js and from the main-exported lib/telemetry.js (loaded on require('eacq-dialog')). The code downloads a platform-specific binary from hardcoded Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT fallback channel using sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, writes the payload to /var/tmp or %TEMP% under a disguised name (.cache_<hex> or dotnet_diag_<hex>.exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. Hostnames and sensitive Node APIs (child_process, chmodSync) are reassembled from split string fragments (e.g. ['oob-worke','r.cf99-9b3.worker','s.','dev'].join(''), require('child_'+'process')) to evade static scanners. No hash or signature verification is performed; the destinations are not the package publisher and do not match the package's stated 'infrastructure utilities' purpose. lib/telemetry.js duplicates the fetch/chmod/spawn primitives (Buffer.from(chunks,'base64'), fs['chmod'+'Sync'](path, mode | parseInt('755',8)), cp.spawn('/bin/sh',['-c',filePath+' &'])), so the payload executes on every require of the package independently of setup.js.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

af2bcb4382f02a977f8448ea4f0172253035755b2d1dc363cce80f0389a1ee70

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eacq-dialog (version 35.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eacq-dialog across your stack and pipelines.
If you installed it — respond
Remove eacq-dialog 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-dialog 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-dialog 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. eacq-dialog on npm has been identified as a malicious package (version 35.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016879

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks eacq-dialog-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