boxy-lazy-loader
Pluggable boxy lazy loader interface
This report shows the evidence for boxy-lazy-loader@35.7.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 a concrete import-time staged-payload chain culminating in detached arbitrary native-code execution, unrelated to the advertised lazy-loader interface.
Decision evidence
public snapshot- index.js imports ./_ext on every package import.
- _ext.js downloads platform-specific binary payloads over HTTPS.
- _ext.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- _ext.js writes payloads to temporary storage, chmods them, then detached-spawns them.
- Payload hosts are obfuscated Cloudflare Workers domains unrelated to the stated loader API.
- package.json has no lifecycle scripts.
- No credential harvesting or AI-agent configuration writes were found.
Source & flagged code
3 flagged · loading sourceA package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_ext.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to boxy-lazy-loader@35.7.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-lazy-loader@35.7.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.