registry / Remote code execution / boxy-use-calls
boxy-use-calls
Shared boxy use calls library for backend integration
This report shows the evidence for boxy-use-calls@35.1.8, 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-code-execution chain, not telemetry: it retrieves opaque binaries and executes them silently. The absence of lifecycle hooks does not mitigate runtime import execution.
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
Arbitrary attacker-controlled native code execution under the importing process user.
Mechanism
import-time remote payload download, drop, chmod, and detached execution
Attack narrative
A normal import reaches _bridge.js without user opt-in. The bridge selects a platform payload, downloads it from obfuscated workers.dev hosts or reconstructs it from DNS TXT records, writes it into temporary storage, sets execute permission on non-Windows systems, then launches it through a detached shell or cmd.exe process.
AI rationale
This is a concrete import-time remote-code-execution chain, not telemetry: it retrieves opaque binaries and executes them silently. The absence of lifecycle hooks does not mitigate runtime import execution.
Evidence
package.jsonindex.js_bridge.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints8
oob-worker.cf103-070.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf99-9b3.workers.devoob-worker.cf100-416.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 _bridge on every package import.
- _bridge.js downloads platform binaries from four obfuscated workers.dev hosts.
- _bridge.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- _bridge.js writes payloads to /var/tmp or Windows temp, marks executable, and detached-spawns them.
- lib/telemetry.js contains a duplicate configurable download-to-execute loader.
Evidence against
- package.json has no lifecycle scripts.
- No source evidence of credential collection before payload execution.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
6 flagged · loading sourcelib/telemetry.jsView file
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L120: const _logger = new Logger(
L121: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L122: );
...
L228: "BUILD_NUMBER",
L229: "GITHUB_ACTIONS",
L230: "GITLAB_CI",
...
L279: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L280: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27494L495: fork() {
L496: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = tinkoff-statist-browser-typed-client-sme.platform.web.companyprofile.metrics@20.2.7
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:20.2.7
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/telemetry.jsFindings
2 Critical3 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_bridge.js
HighChild Processlib/telemetry.js
HighKnown Malware Source Similaritylib/telemetry.js
HighKnown Malware Source Similarity_bridge.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to boxy-use-calls@35.1.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-use-calls@35.1.8. 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.