registry / Remote code execution / dolyame-boxy-stories-of-block
dolyame-boxy-stories-of-block
Dolyame boxy stories of block abstraction layer
This report shows the evidence for dolyame-boxy-stories-of-block@35.8.6, 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 unrelated to the package's advertised abstraction API. The bundled telemetry source duplicates the same downloader/executor pattern but is not needed to establish the attack.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any require/import of the package entrypoint.
Impact
Arbitrary native code execution under the importing user's privileges.
Mechanism
Remote payload download via HTTPS/DNS followed by temp-file execution.
Attack narrative
At import time, index.js silently loads _support.js. Its bootstrap selects a platform payload, downloads it from hard-coded Workers hosts or reconstructs it from DNS TXT records, writes it to a hidden/random temporary file, marks it executable on Unix, and launches it detached through a shell or cmd.exe. The marker only limits repeat execution; opt-out variables do not make this consented behavior.
AI rationale
This is a concrete import-time remote-code execution chain unrelated to the package's advertised abstraction API. The bundled telemetry source duplicates the same downloader/executor pattern but is not needed to establish the attack.
Evidence
package.jsonindex.js_support.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_state
Network endpoints7
oob-worker.cf99-9b3.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf103-070.workers.devsdk.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 _support.js at module load.
- _support.js downloads platform binaries over HTTPS and DNS TXT.
- _support.js writes payloads to temp storage, chmods them, then detached-spawns them.
- Downloads are hidden behind generic analytics names and errors are suppressed.
- No integrity verification is performed despite the comment claiming one.
Evidence against
- package.json has no lifecycle scripts.
- lib/telemetry.js is not imported by the public entrypoint.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_support.jsView file
4const crypto = require("crypto");
L5: const https = require("https");
L6: const path = require("path");
...
L43: const MAX_AGE = 23009;
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");
...
L93: try {
L94: require("dns").resolveTxt(d, (e, rr) => {
L95: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_support.jsView on unpkg · L44Trigger-reachable chain: manifest.main -> index.js -> _support.js
L4: const crypto = require("crypto");
L5: const https = require("https");
L6: const path = require("path");
...
L43: const MAX_AGE = 23009;
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");
...
L93: try {
L94: require("dns").resolveTxt(d, (e, rr) => {
L95: 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.
_support.jsView on unpkg · L4Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_support.js
CriticalTrigger Reachable Dangerous Capability_support.js
HighChild Process_support.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to dolyame-boxy-stories-of-block@35.8.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-stories-of-block@35.8.6. 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.