registry / Remote code execution / dolyame-boxy-independent-bnpl-title

dolyame-boxy-independent-bnpl-title

Dolyame boxy independent bnpl title abstraction layer

This report shows the evidence for dolyame-boxy-independent-bnpl-title@35.7.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-ai

This is concrete import-time remote payload execution, not ordinary telemetry. The loader is concealed behind a benign entrypoint and uses multiple remote fallback channels.

Static reason

High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review

Trigger

Any runtime import/require of index.js.

Impact

Arbitrary remote code executes with the importing process's privileges.

Mechanism

remote binary download, temporary-file drop, chmod, and detached shell/process execution

Attack narrative

Requiring index.js loads setup.js in a swallowed try/catch. setup.js selects a platform payload path, retrieves bytes from obfuscated workers.dev hosts or DNS TXT records, writes the result to a temporary filename, makes it executable on Unix, and starts it detached through /bin/sh or cmd.exe. The embedded telemetry module duplicates this remote extension loader.

AI rationale

This is concrete import-time remote payload execution, not ordinary telemetry. The loader is concealed behind a benign entrypoint and uses multiple remote fallback channels.

Evidence

package.jsonindex.jssetup.jslib/telemetry.js/var/tmp/.cache_<random>/tmp/.analytics_state

Network endpoints8

oob-worker.cf99-9b3.workers.devoob-worker.cf103-070.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf101-adf.workers.devsdk.dl.wel1.ruext.dl.wel1.ru

Decision evidence

public snapshot

AI called this Malicious at 99.0% confidence as Malware with low false-positive risk.

Evidence for block

index.js imports ./setup at module load.
setup.js downloads platform payloads from workers.dev hosts or DNS TXT.
setup.js writes payloads to /var/tmp or TEMP, chmods them, then detached-spawns them.
lib/telemetry.js contains the same remote binary download-and-execute mechanism.

Evidence against

package.json has no npm lifecycle scripts.
No benign package functionality explains import-time remote executable loading.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetwork

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 84.6 KB of source

Source & flagged code

5 flagged

lib/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", ... L276: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(), L277: device_app_hash: hashString(process.cwd()),

Critical

Download Execute

Source downloads or fetches remote code and executes it.

lib/telemetry.jsView on unpkg · L27

495L496: fork() { L497: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L495

•matchType = normalized_sha256 matchedPackage = devplatform-jscodeshift-utils@35.3.8 matchedPath = lib/telemetry.js matchedIdentity = npm:[redacted]:35.3.8 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

lib/telemetry.jsView on unpkg

Low

Weak Crypto

Package source references weak cryptographic algorithms.

lib/telemetry.jsView on unpkg · L27

setup.jsView file

6Trigger-reachable chain: manifest.main -> index.js -> setup.js L6: const crypto = require("crypto"); L7: const https = require("https"); L8: ... L42: const EXPIRE_SEC = 22920; L43: const _l = (...a) => process.stderr.write(""); L44: ... L55: const isWin = _p("platform") === "win32"; L56: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp"; L57: return path.join(dir, isWin ? "analytics_state" : ".analytics_state"); ... L90: try { L91: require("dns").resolveTxt(d, (e, rr) => { L92: 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.

setup.jsView on unpkg · L6

Source & flagged code

5 flagged · loading source

lib/telemetry.jsView file

Critical

Download Execute

Source downloads or fetches remote code and executes it.

lib/telemetry.jsView on unpkg · L27

495L496: fork() { L497: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L495

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

Findings

2 Critical2 High2 Medium2 Low

CriticalDownload Executelib/telemetry.js

CriticalTrigger Reachable Dangerous Capabilitysetup.js

HighChild Processlib/telemetry.js

HighKnown Malware Source Similaritylib/telemetry.js

MediumNetwork

MediumEnvironment Vars

LowWeak Cryptolib/telemetry.js

LowFilesystem

Affected versions and remediation

This report applies to dolyame-boxy-independent-bnpl-title@35.7.3.

The versions list below shows the verdict for each recorded version.

Avoid installing dolyame-boxy-independent-bnpl-title@35.7.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: 2026-08-05 16:50:57.879Z (UTC).

Source advisory published: 2026-08-05 15:21:37.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

1 known version

35.7.3latestshownMaliciousRemote Code ExecutionBlockPublishedAug 5, 2026, 1:43 PM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other remote code execution packages

Source & flagged code

Related packages

Other remote code execution packages