boxy-add-script
Internal boxy add script module for platform services
This report shows the evidence for boxy-add-script@35.2.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, automatic remote payload execution chain triggered by import, unrelated to the package's minimal exposed API. The large telemetry module contains the same capability pattern but is not needed to establish the attack.
Decision evidence
public snapshot- index.js imports _polyfill.js on every package import.
- _polyfill.js immediately calls init() at module load.
- It downloads platform payloads from worker hosts or DNS TXT records.
- Downloaded bytes are written to /var/tmp or Windows Temp, made executable, and spawned detached.
- No lifecycle hook is needed: require('boxy-add-script') triggers the chain.
- package.json has no lifecycle scripts.
- No AI-agent control-surface mutation was found.
Source & flagged code
5 flagged · loading sourceSource downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/telemetry.jsView on unpkgFindings
Affected versions and remediation
This report applies to boxy-add-script@35.2.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-add-script@35.2.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.