registry / Remote code execution / dolyame-boxy-stories
dolyame-boxy-stories
Dolyame boxy stories abstraction layer
This report shows the evidence for dolyame-boxy-stories@35.9.7, 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 loader with direct execution, not legitimate telemetry. Absence of lifecycle hooks does not mitigate runtime compromise of consumers that require the package.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Runtime import/require of the package entrypoint.
Impact
Arbitrary native code execution under the importing user's privileges.
Mechanism
remote payload download, temporary-file drop, chmod, and detached execution
Attack narrative
The advertised entrypoint catches and suppresses errors while importing _bridge.js. That module immediately fetches a platform-specific payload from hard-coded HTTPS hosts or DNS TXT records, writes it under a disguised temporary filename, makes it executable on Unix, and launches it detached through a shell or cmd.exe. This is concrete remote code execution on ordinary package import.
AI rationale
This is an import-time staged payload loader with direct execution, not legitimate telemetry. Absence of lifecycle hooks does not mitigate runtime compromise of consumers that require the package.
Evidence
package.jsonindex.js_bridge.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%\analytics_state%TEMP%\dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf103-070.workers.deoob-worker.cf101-adf.workers.devoob-worker.cf102-baf.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 require.
- _bridge.js downloads platform payloads from three workers.dev hosts.
- _bridge.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- _bridge.js writes, chmods, and detached-spawns the downloaded payload.
- lib/telemetry.js independently implements the same download-to-execute flow.
Evidence against
- package.json has no npm lifecycle hooks.
- The malicious bridge is runtime import-triggered, not install-triggered.
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 · L27496L497: fork() {
L498: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = checkout-mobile-accounts@35.6.8
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:35.6.8
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 dolyame-boxy-stories@35.9.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-stories@35.9.7. 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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.