registry / Remote code execution / dolyame-boxy-independent-bnpl-cards
dolyame-boxy-independent-bnpl-cards
Reusable dolyame boxy independent bnpl cards components
This report shows the evidence for dolyame-boxy-independent-bnpl-cards@35.7.6. 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 remote payload execution chain unrelated to the stated component SDK. Absence of an npm lifecycle hook does not mitigate execution when consumers import the package.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any runtime require/import of the package entry point.
Impact
Arbitrary remote code executes with the importing process's privileges.
Mechanism
import-time remote binary download, drop, and detached execution
Attack narrative
The advertised entry point silently requires setup.js. Unless opt-out environment variables are set, it fetches a platform-specific payload from obfuscated Workers hosts or reconstructs it from DNS TXT records, stores it under a randomized temporary filename, makes it executable on Unix, and launches it detached through cmd.exe or /bin/sh. The same binary-loader design also appears in lib/telemetry.js.
AI rationale
This is a concrete, import-time remote payload execution chain unrelated to the stated component SDK. Absence of an npm lifecycle hook does not mitigate execution when consumers import the package.
Evidence
package.jsonindex.jssetup.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints8
oob-worker.cf9-9b3.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf100-416.workers.devoob-worker.cf103-070.workers.devsdk.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 setup.js on package require.
- setup.js downloads platform binaries over HTTPS.
- setup.js falls back to DNS TXT payload retrieval.
- Downloaded bytes are written to /var/tmp or temp and executed via shell.
- Remote hosts and payload paths are obfuscated by string concatenation.
Evidence against
- package.json has no lifecycle scripts.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading sourcelib/telemetry.jsView file
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L116: const _logger = new Logger(
L117: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L118: );
...
L224: "BUILD_NUMBER",
L225: "GITHUB_ACTIONS",
L226: "GITLAB_CI",
...
L275: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L276: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27498L499: fork() {
L500: const child = new Scope();
High
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L116: const _logger = new Logger(
L117: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L118: );
...
L224: "BUILD_NUMBER",
L225: "GITHUB_ACTIONS",
L226: "GITLAB_CI",
...
L275: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L276: device_app_hash: hashString(process.cwd()),
Low
Weak Crypto
Findings
2 Critical1 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capabilitysetup.js
HighChild Processlib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to dolyame-boxy-independent-bnpl-cards@35.7.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-independent-bnpl-cards@35.7.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.