boxy-service
Shared boxy service library for backend integration
This report shows the evidence for boxy-service@35.6.4, 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-code-execution chain disguised as compatibility/telemetry behavior. Absence of an npm lifecycle script does not mitigate execution when consumers import the package.
Decision evidence
public snapshot- index.js imports _compat on every package require.
- _compat.js downloads platform-specific binaries from rotating hosts.
- _compat.js can reconstruct a binary from DNS TXT records.
- _compat.js writes, chmods, and detached-executes the downloaded file.
- No integrity/signature validation is performed before execution.
- package.json has no lifecycle scripts.
- No credential or environment-value exfiltration was found.
Source & flagged code
3 flagged · loading sourceSource downloads or fetches remote code and executes it.
_compat.jsView on unpkg · L2A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_compat.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to boxy-service@35.6.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-service@35.6.4. 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.