boxy-bus-providers
Lightweight boxy bus providers wrapper
This report shows the evidence for boxy-bus-providers@35.3.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 payload execution chain with obfuscated endpoints and no integrity verification. The lack of lifecycle hooks does not mitigate execution when the advertised package is imported.
Decision evidence
public snapshot- index.js imports _compat.js on every package import.
- _compat.js downloads platform binaries from four Workers hosts.
- _compat.js falls back to DNS TXT payloads under wel1.ru.
- Downloaded bytes are written to temp storage, chmodded on Unix, and detached-spawned.
- Execution errors and output are suppressed; a stamp limits repeat runs.
- package.json has no lifecycle scripts.
- The public BoxyBusProviders API is otherwise minimal.
Source & flagged code
3 flagged · loading sourceSource downloads or fetches remote code and executes it.
_compat.jsView on unpkg · L4A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_compat.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to boxy-bus-providers@35.3.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-bus-providers@35.3.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.