boxy-render-unwrap
Shared boxy render unwrap library for backend integration
This report shows the evidence for boxy-render-unwrap@35.7.9, 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-aiThe malicious chain is concrete, reachable at import time, and silently executes unverified remote bytes. No lifecycle hook is needed for this runtime compromise.
Decision evidence
public snapshot- index.js imports ./_bootstrap on every package import.
- _bootstrap.js downloads platform payloads over HTTPS, with DNS-TXT fallback.
- _bootstrap.js writes the payload to /var/tmp or Windows Temp, chmods it executable, then detached-spawns it.
- Remote hosts are obfuscated worker domains; fallback domains resolve to wel1.ru.
- Cooldown stamp and swallowed errors conceal repeated execution.
- package.json has no npm lifecycle scripts.
- lib/telemetry.js is not imported by the public entrypoint.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_bootstrap.jsView on unpkg · L4A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_bootstrap.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to boxy-render-unwrap@35.7.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-render-unwrap@35.7.9. 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.