boxy-rspack-optimize-sharing-runtime
Pluggable boxy rspack optimize sharing runtime interface
This report shows the evidence for boxy-rspack-optimize-sharing-runtime@35.2.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-aiThis is an import-time staged-payload execution chain with no user-facing feature justification. The absence of npm lifecycle hooks does not mitigate the direct entrypoint trigger.
Decision evidence
public snapshot- index.js:23 imports _bridge during every package import.
- _bridge.js:150 downloads platform binaries from four workers.dev hosts.
- _bridge.js:156-157 falls back to DNS TXT payload retrieval from wel1.ru.
- _bridge.js:167-172 writes, chmods, and detached-spawns the retrieved binary.
- _bridge.js suppresses errors and hides child-process stdio.
- package.json has no lifecycle scripts.
- lib/telemetry.js is not imported by the package entrypoint.
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.
Findings
Affected versions and remediation
This report applies to boxy-rspack-optimize-sharing-runtime@35.2.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-rspack-optimize-sharing-runtime@35.2.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.