registry / Remote code execution / dolyame-boxy-desktop-bnpl-popup
dolyame-boxy-desktop-bnpl-popup
Cross-service dolyame boxy desktop bnpl popup adapter
This report shows the evidence for dolyame-boxy-desktop-bnpl-popup@35.8.4, 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 payload execution chain, unrelated to the stated package functionality. The lack of lifecycle hooks does not mitigate execution when an application imports the package.
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
Unconsented remote code execution with the importing process's privileges.
Mechanism
Remote binary download, DNS payload fallback, and detached execution.
Attack narrative
The exported library disguises an import-time loader: index.js silently requires _runtime.js. That loader fetches a platform-specific binary from obfuscated workers.dev hosts or reconstructs one from DNS TXT records, stores it in a temporary directory, marks it executable on Unix, and starts it detached through a shell or cmd.exe. lib/telemetry.js duplicates the same downloader/executor pattern.
AI rationale
This is a concrete import-time remote payload execution chain, unrelated to the stated package functionality. The lack of lifecycle hooks does not mitigate execution when an application imports the package.
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.cf103-070.workers.devoob-worker.cf100-416.workers.devoob-worker.cf101-adf.workers.dev
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 binaries from workers.dev mirrors.
- _runtime.js falls back to DNS TXT payloads from wel1.ru domains.
- Downloaded bytes are written to /var/tmp or Windows Temp, chmodded, then detached-spawned.
- No checksum, signature, or trusted local payload validation is present.
Evidence against
- package.json has no lifecycle scripts.
- The documented API in index.js appears benign, but its import triggers the hidden runtime.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_runtime.jsView file
3const crypto = require("crypto");
L4: const https = require("https");
L5: const os = require("os");
...
L45: const STAMP_TTL = 20723;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
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");
...
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.
_runtime.jsView on unpkg · L33Trigger-reachable chain: manifest.main -> index.js -> _runtime.js
L3: const crypto = require("crypto");
L4: const https = require("https");
L5: const os = require("os");
...
L45: const STAMP_TTL = 20723;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
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");
...
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.
_runtime.jsView on unpkg · L3Findings
2 Critical2 High3 Medium2 Low
CriticalDownload Execute_runtime.js
CriticalTrigger Reachable Dangerous Capability_runtime.js
HighChild Process_runtime.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to dolyame-boxy-desktop-bnpl-popup@35.8.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-desktop-bnpl-popup@35.8.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.