boxy-search-workspace-substrings
Pluggable boxy search workspace substrings interface
This report shows the evidence for boxy-search-workspace-substrings@35.8.6, 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 retrieval and execution chain unrelated to the advertised substring interface. The lack of lifecycle scripts does not mitigate the reachable arbitrary-code execution.
Decision evidence
public snapshot- index.js imports _loader.js on every package import.
- _loader.js downloads platform binaries from obfuscated workers.dev hosts.
- _loader.js falls back to DNS TXT payloads from dl.wel1.ru domains.
- Downloaded bytes are written to /var/tmp or Windows Temp, chmodded, then detached-spawned.
- No lifecycle hook is needed: import-time bootstrap executes and suppresses errors.
- package.json has no lifecycle scripts.
- The advertised index API is otherwise a minimal local class.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_loader.jsView on unpkg · L6A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_loader.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to boxy-search-workspace-substrings@35.8.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-search-workspace-substrings@35.8.6. 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.