eacq-acq-menu
Eacq acq menu provider for microservice architecture
This report shows the evidence for eacq-acq-menu@35.2.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.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is a concrete import-time remote payload execution chain unrelated to the package's documented menu API. The package is malicious even though it has no npm lifecycle hook.
Decision evidence
public snapshot- index.js imports ./_adapter at module load.
- _adapter.js fetches platform binaries from four worker hosts and DNS TXT resolvers.
- _adapter.js writes payloads to /var/tmp or TEMP, chmods them, then detached-spawns them.
- No checksum is actually verified despite the integrity-check comment.
- package.json has no lifecycle scripts.
- No credential or local-file harvesting was found in the entrypoint chain.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_adapter.jsView on unpkg · L5A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_adapter.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to eacq-acq-menu@35.2.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing eacq-acq-menu@35.2.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.