registry / Remote code execution / boxy-legacy-providers
boxy-legacy-providers
Pluggable boxy legacy providers interface
This report shows the evidence for boxy-legacy-providers@35.6.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 staged-payload chain, not package-aligned telemetry. It enables arbitrary remote code execution without user action.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of index.js.
Impact
Unconsented arbitrary native code execution under the importing process account.
Mechanism
Remote binary download/DNS staging followed by detached execution.
Attack narrative
index.js suppresses errors while requiring _shim.js, whose top-level main() runs on import. The shim selects a platform payload path, retrieves a binary from obfuscated workers.dev hosts, or reconstructs one from DNS TXT records under dl.wel1.ru. A payload over 1000 bytes is written under a random temporary name, marked executable on Unix, and launched through a detached shell or cmd.exe process. The downloaded content has no enforced hash or signature validation.
AI rationale
This is a concrete import-time staged-payload chain, not package-aligned telemetry. It enables arbitrary remote code execution without user action.
Evidence
package.jsonindex.js_shim.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf101-adf.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf103-070.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.runet.dl.wel1.ru
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _shim.js on every package import.
- _shim.js fetches platform payloads from workers.dev mirrors.
- _shim.js falls back to DNS TXT payloads from dl.wel1.ru.
- _shim.js writes the payload to temp storage, chmods it, then detached-spawns it.
- No payload integrity verification is implemented despite the comment.
Evidence against
- package.json has no lifecycle scripts.
- No credential or environment-value harvesting was found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_shim.jsView file
5const fs = require("fs");
L6: const https = require("https");
L7: const path = require("path");
...
L43: const TTL = 23230;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: if (e || !rr || !rr.length) return r("");
Critical
5Trigger-reachable chain: manifest.main -> index.js -> _shim.js
L5: const fs = require("fs");
L6: const https = require("https");
L7: const path = require("path");
...
L43: const TTL = 23230;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: if (e || !rr || !rr.length) return r("");
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_shim.jsView on unpkg · L5118
Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_shim.js
CriticalTrigger Reachable Dangerous Capability_shim.js
HighChild Process_shim.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to boxy-legacy-providers@35.6.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-legacy-providers@35.6.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.