Which versions of eacq-cdk are malicious?

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

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

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

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

Yes — eacq-cdk is associated with the IN-MAL-2026-016892 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-cdk 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-cdk (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-cdk across your stack and pipelines.

Malicious package

eacq-cdknpm

eacq-cdk is a confirmed malicious npm package (MAL-2026-13513) 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-cdk (npm)

MAL-2026-13513

Immediate action

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

npm uninstall eacq-cdk

What this malware does

Requiring the package executes _init.js, which selects a platform-specific payload path and fetches an executable over HTTPS from Cloudflare Workers hosts whose names are assembled via.join('') from character-shard arrays (oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev). If HTTPS retrieval fails, the loader falls back to base64-encoded payload delivery over DNS TXT queries under *.dl.wel1.ru. The fetched bytes are written to a hidden filename under /tmp (or Windows Temp), chmod 0755'd, and spawned detached via spawn('/bin/sh',...) / spawn('cmd',...). The destinations are unrelated to any legitimate publisher, the hostnames are split across arrays to defeat static string search, and the behavior is framed as 'telemetry/analytics'. Any project that installs this package hands full-host code execution to the operator of those endpoints on first require.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

0fdb6bb562df94959130d84e06dc14aa40e9347c60da24dd32ce672024c2e0aa

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-cdk (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-cdk across your stack and pipelines.
If you installed it — respond
Remove eacq-cdk 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-cdk 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-cdk 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-cdk 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-016892

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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