registry / Remote code execution / eacq-acq-menu-core
eacq-acq-menu-core
base framework module
This report shows the evidence for eacq-acq-menu-core@35.9.7, 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.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is an import-time staged native payload execution chain unrelated to the package’s stated framework purpose. The absence of an npm lifecycle hook does not mitigate execution on normal module import.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any require/import of index.js
Impact
Arbitrary native code execution as the importing user.
Mechanism
Remote payload download, disk drop, and detached execution
Attack narrative
Requiring index.js suppresses errors while loading _helpers.js, whose setup runs immediately. It selects a platform payload URL, downloads an opaque binary from rotating worker hosts or reconstructs one from DNS TXT records, writes it to a temporary path, marks it executable on Unix, and launches it detached via a shell or cmd.exe. The payload is neither authenticated nor inspected.
AI rationale
This is an import-time staged native payload execution chain unrelated to the package’s stated framework purpose. The absence of an npm lifecycle hook does not mitigate execution on normal module import.
Evidence
package.jsonindex.js_helpers.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints6
oob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packageDNS TXT: sdk.dl.wel1.ruDNS TXT: ext.dl.wel1.ruDNS TXT: pkg.dl.wel1.ru
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _helpers.js at package import time.
- _helpers.js downloads platform binaries from rotating hosts.
- DNS TXT fallback reconstructs a base64 payload.
- Downloaded bytes are written, chmodded, and detached-spawned.
- No payload integrity or signature verification is present.
Evidence against
- package.json has no lifecycle scripts.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
3 flagged · loading source_helpers.jsView file
3const fs = require("fs");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L43: const TTL = 23129;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_helpers.jsView on unpkg · L33Trigger-reachable chain: manifest.main -> index.js -> _helpers.js
L3: const fs = require("fs");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L43: const TTL = 23129;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: if (e || !rr || !rr.length) return r("");
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_helpers.jsView on unpkg · L3Findings
2 Critical1 High2 Medium1 Low
CriticalDownload Execute_helpers.js
CriticalTrigger Reachable Dangerous Capability_helpers.js
HighChild Process_helpers.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to eacq-acq-menu-core@35.9.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing eacq-acq-menu-core@35.9.7. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.