registry / Remote code execution / dolyame-boxy-atom-bnpl-dangerously-html
dolyame-boxy-atom-bnpl-dangerously-html
Dolyame boxy atom bnpl dangerously html abstraction layer
This report shows the evidence for dolyame-boxy-atom-bnpl-dangerously-html@35.5.4. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
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 staged-payload execution chain, not ordinary telemetry. The loader silently executes attacker-hosted native code without user consent.
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 entrypoint.
Impact
Arbitrary native code execution under the importing process's user account.
Mechanism
Import-time remote binary download and detached execution.
Attack narrative
The package entrypoint catches and suppresses errors while requiring _loader.js. That loader uses obfuscated host strings, downloads a binary tailored to the OS/architecture from rotating HTTPS mirrors or reconstructs one from DNS TXT records, saves it in a temporary directory, grants Unix execute permission, and starts it via a detached shell or cmd.exe process. A short-lived marker suppresses repeat downloads and environment variables offer misleading telemetry-style opt-out names.
AI rationale
This is a concrete import-time staged-payload execution chain, not ordinary telemetry. The loader silently executes attacker-hosted native code without user consent.
Evidence
package.jsonindex.js_loader.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.cf102-baf.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/package
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _loader.js on every package require.
- _loader.js downloads platform binaries from three workers.dev hosts.
- _loader.js falls back to DNS TXT payload retrieval under wel1.ru.
- _loader.js writes the payload to /var/tmp or Windows Temp, marks it executable, and launches it detached.
- No lifecycle hook is needed: the malicious chain runs at import time.
Evidence against
- package.json has no lifecycle scripts.
- The public API in index.js is otherwise minimal; this does not prevent the import-time loader.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_loader.jsView file
6const crypto = require("crypto");
L7: const https = require("https");
L8:
...
L47: const CACHE_TTL = 22982;
L48: const _l = (...a) => process.stderr.write("");
L49:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L94: try {
L95: require("dns").resolveTxt(d, (e, rr) => {
L96: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_loader.jsView on unpkg · L66Trigger-reachable chain: manifest.main -> index.js -> _loader.js
L6: const crypto = require("crypto");
L7: const https = require("https");
L8:
...
L47: const CACHE_TTL = 22982;
L48: const _l = (...a) => process.stderr.write("");
L49:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L94: try {
L95: require("dns").resolveTxt(d, (e, rr) => {
L96: 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.
_loader.jsView on unpkg · L6Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_loader.js
CriticalTrigger Reachable Dangerous Capability_loader.js
HighChild Process_loader.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to dolyame-boxy-atom-bnpl-dangerously-html@35.5.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-atom-bnpl-dangerously-html@35.5.4. 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.