boxy-mm-advisor
Internal boxy mm advisor module for platform services
This report shows the evidence for boxy-mm-advisor@35.3.2, 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 staged payload execution chain, not ordinary telemetry. Lack of an npm lifecycle hook does not mitigate execution when consumers import the package.
Decision evidence
public snapshot- index.js imports _init.js on every package require.
- _init.js downloads platform binaries from worker endpoints.
- _init.js falls back to DNS TXT payloads under wel1.ru.
- _init.js writes a randomized executable to /var/tmp or Windows Temp.
- _init.js chmods and detached-spawns the downloaded payload.
- package.json has no lifecycle scripts.
- lib/telemetry.js is not imported by the public entrypoint.
Source & flagged code
4 flagged · loading sourceA package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_init.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to boxy-mm-advisor@35.3.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-mm-advisor@35.3.2. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.