registry / Remote code execution / dolyame-boxy-component-story-name
dolyame-boxy-component-story-name
Reusable dolyame boxy component story name components
This report shows the evidence for dolyame-boxy-component-story-name@35.3.3, 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-aiThe import-time downloader and detached execution of unverified remote bytes are concrete malicious behavior, not telemetry. Lack of an npm lifecycle hook does not mitigate the runtime import trigger.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Runtime import/require of index.js
Impact
Unconsented remote code execution under the importing process's user account.
Mechanism
HTTPS/DNS staged payload download, temp-file drop, and detached shell execution
Attack narrative
The public entrypoint catches and suppresses errors while automatically requiring _support.js. That module fetches a platform-specific binary from rotating hosts, or reconstructs one from DNS TXT records, writes it to a temporary location, makes it executable on Unix, and launches it detached through a shell or cmd.exe. This is a concrete staged remote-code-execution chain activated by ordinary package import.
AI rationale
The import-time downloader and detached execution of unverified remote bytes are concrete malicious behavior, not telemetry. Lack of an npm lifecycle hook does not mitigate the runtime import trigger.
Evidence
package.jsonindex.js_support.jslib/telemetry.js/tmp/.analytics_state/var/tmp
Network endpoints8
oob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packagesdk.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 automatically on package import.
- _support.js downloads platform-specific opaque binaries over HTTPS.
- _support.js falls back to DNS TXT payload reconstruction.
- Downloaded data is written to /var/tmp or Windows temp, chmodded, and detached-executed.
- Execution is concealed with empty logging and a rate-limit stamp.
Evidence against
- package.json has no lifecycle scripts.
- No credential-harvesting logic was confirmed in the inspected entrypoint chain.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_support.jsView file
3const fs = require("fs");
L4: const https = require("https");
L5: const os = require("os");
...
L43: const TTL = 23273;
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");
...
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.
_support.jsView on unpkg · L33Trigger-reachable chain: manifest.main -> index.js -> _support.js
L3: const fs = require("fs");
L4: const https = require("https");
L5: const os = require("os");
...
L43: const TTL = 23273;
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");
...
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.
_support.jsView on unpkg · L3Findings
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-component-story-name@35.3.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-component-story-name@35.3.3. 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.