eacq-core
This report shows the evidence for eacq-core@35.8.1, the only known version.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-13514 confirms this npm version as malicious.
Advisory
MAL-2026-13514
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in eacq-core (npm)
Details
On require() of eacq-core, both _helpers.js and lib/telemetry.js download a platform-specific binary from Cloudflare Workers hosts assembled at runtime via string-splitting (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT fallback to *.dl.wel1.ru, write the bytes to /tmp/.cache_<rand> or %TEMP%\dotnet_diag_<rand>.exe, chmod 0755 (via fs['chmod'+'Sync']), and spawn the file detached through '/bin/sh -c <path> &' or 'cmd /c start'. No hash or signature verification is performed and the destinations are unrelated to any legitimate publisher. child_process is loaded through require('child_'+'process') and hostnames are assembled via.join('') to evade static analysis. Cover-story comments framing the code as an 'Analytics SDK' with 'opt-out env vars' accompany the payload. The fetch-and-execute chain fires unconditionally at module load, giving whoever controls the Workers hosts arbitrary code execution on any machine that installs or imports this package.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to eacq-core@35.8.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing eacq-core@35.8.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.