registry / Remote code execution / dolyame-boxy-block
dolyame-boxy-block
Dolyame boxy block abstraction layer
This report shows the evidence for dolyame-boxy-block@35.5.2, 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 automatic remote payload execution unrelated to the documented abstraction API. No install hook is needed because ordinary package import activates the chain.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any Node.js require/import of the package main entrypoint.
Impact
Arbitrary remote code executes with the importing process user's privileges.
Mechanism
remote binary download, DNS fallback, and detached execution
Attack narrative
The public entrypoint silently requires _runtime.js. On import, it fetches a platform-specific payload from rotating Workers hosts or reconstructs one from DNS TXT records, writes it to a temporary location, marks it executable on Unix, and spawns it detached through /bin/sh or cmd.exe. The execution is hidden and repeat runs are suppressed by a temporary marker.
AI rationale
This is concrete automatic remote payload execution unrelated to the documented abstraction API. No install hook is needed because ordinary package import activates the chain.
Evidence
package.jsonindex.js_runtime.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packagesdk.dl.wel1.ruext.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 _runtime.js on every package import.
- _runtime.js downloads platform payloads from rotating workers.dev hosts.
- _runtime.js falls back to DNS TXT payload retrieval from dl.wel1.ru domains.
- Downloaded bytes are written as executable files in /var/tmp or Windows Temp.
- _runtime.js chmods Unix payloads and launches them detached via shell/cmd.
- A short-lived /tmp marker suppresses repeat execution.
Evidence against
- package.json has no lifecycle scripts.
- No credential or project-file harvesting was found in the entrypoint chain.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_runtime.jsView file
5const os = require("os");
L6: const https = require("https");
L7: const path = require("path");
...
L44: const STAMP_TTL = 21405;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
L57: const isWin = _p("platform") === "win32";
L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L59: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_runtime.jsView on unpkg · L55Trigger-reachable chain: manifest.main -> index.js -> _runtime.js
L5: const os = require("os");
L6: const https = require("https");
L7: const path = require("path");
...
L44: const STAMP_TTL = 21405;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
L57: const isWin = _p("platform") === "win32";
L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L59: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: 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.
_runtime.jsView on unpkg · L5Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_runtime.js
CriticalTrigger Reachable Dangerous Capability_runtime.js
HighChild Process_runtime.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to dolyame-boxy-block@35.5.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-block@35.5.2. 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.