Which versions of eacq-auth are malicious?

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

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

eacq-auth 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.

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

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

Yes — eacq-auth is associated with the IN-MAL-2026-015566 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-auth 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-auth (version 35.4.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eacq-auth across your stack and pipelines.

Malicious package

eacq-authnpm

eacq-auth is a confirmed malicious npm package (MAL-2026-13208) that steals credentials and exfiltrates sensitive data (malicious version 35.4.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eacq-auth (npm)

MAL-2026-13208

Immediate action

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

npm uninstall eacq-auth

What this malware does

index.js exports a benign TokenManager facade but silently require('./_bootstrap') in a try/catch on load. bootstrap.js selects a platform-specific asset, downloads an unverified binary from hardcoded Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev) — with a DNS-TXT chunked-fetch fallback under *.dl.wel1.ru — writes it to /tmp or %TEMP% under a disguised name (e.g. dotnet_diag,.cache_), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe start /b. Destination hostnames are reconstructed by array.join to evade static string matching. Executes at require() time, so a normal npm install + any downstream import runs the fetched binary on the installer host.

Malicious versions

1 flagged

35.4.8

Indicators of compromise (SHA-256)

44896d37931bf7bf16a6061be03cc11eaaf4dbf05780ac9e2ff49a1990986eb7

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-015566

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks eacq-auth-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database