registry / Remote code execution / boxy-temper
boxy-temper
Cross-service boxy temper adapter
This report shows the evidence for boxy-temper@35.1.5, 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 concrete, import-triggered remote code execution rather than declared telemetry functionality. The lack of an install hook does not mitigate execution during ordinary use.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Runtime require/import of boxy-temper
Impact
Arbitrary remote code executes with the importing process's privileges.
Mechanism
remote payload download, temp-file drop, and detached execution
Attack narrative
At import time, index.js silently requires _bridge.js. The bridge downloads an opaque executable from rotating HTTPS hosts, falling back to DNS TXT chunk retrieval; it stores the content in a temporary executable file and starts it through cmd.exe or /bin/sh in detached mode. A timestamp file throttles repeated execution, and failures are suppressed.
AI rationale
This is concrete, import-triggered remote code execution rather than declared telemetry functionality. The lack of an install hook does not mitigate execution during ordinary use.
Evidence
package.jsonindex.js_bridge.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf103-070.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf99-9b3.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.js on every package import.
- _bridge.js downloads platform binaries from Workers hosts or DNS TXT records.
- _bridge.js writes the payload to temporary storage, chmods it, then detached-spawns it.
- Payload retrieval/execution is hidden behind telemetry/analytics naming and errors are suppressed.
- lib/telemetry.js independently contains the same remote-binary execution mechanism.
Evidence against
- package.json has no lifecycle scripts.
- The public API itself is minimal, but importing it activates the hidden bridge.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
5 flagged · loading sourcelib/telemetry.jsView file
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L116: const _logger = new Logger(
L117: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L118: );
...
L224: "BUILD_NUMBER",
L225: "GITHUB_ACTIONS",
L226: "GITLAB_CI",
...
L275: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L276: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27495L496: fork() {
L497: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = bigops-telephony@35.8.4
matchedPath = lib/telemetry.js
matchedIdentity = npm:Ymlnb3BzLXRlbGVwaG9ueQ:35.8.4
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.jsView on unpkgFindings
2 Critical2 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_bridge.js
HighChild Processlib/telemetry.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to boxy-temper@35.1.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing boxy-temper@35.1.5. 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.