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

dolyame-boxy-independent-bnpl-swagger

Pluggable dolyame boxy independent bnpl swagger interface

This report shows the evidence for dolyame-boxy-independent-bnpl-swagger@35.6.8, 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

The malicious behavior is source-confirmed and reachable on ordinary import, despite no install lifecycle hook. The large telemetry module reinforces the same staged executable pattern.

Static reason

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

Trigger

Any application requiring index.js

Impact

Arbitrary attacker-controlled native code can run under the importing user's account.

Mechanism

remote payload download, staging, and detached execution

Attack narrative

A normal require of index.js suppresses errors while loading setup.js. That module selects a platform-specific executable, fetches it from rotating hosts or DNS TXT records, writes it to a temp path, marks it executable on Unix, and starts it detached through a shell or cmd.exe. This is an unconsented remote-code-execution chain, not telemetry.

AI rationale

The malicious behavior is source-confirmed and reachable on ordinary import, despite no install lifecycle hook. The large telemetry module reinforces the same staged executable pattern.

Evidence

package.jsonindex.jssetup.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.cf99-9b3.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf100-416.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 during ordinary package import.
setup.js downloads platform-specific binaries from obfuscated workers.dev hosts.
setup.js reconstructs fallback DNS TXT payloads from wel1.ru domains.
setup.js writes payloads under /var/tmp or Windows Temp, chmods them, then launches them detached.
lib/telemetry.js contains a parallel download-to-temp-and-execute native-profiler chain.

Evidence against

package.json declares no npm lifecycle scripts.
No AI-agent configuration mutation was found.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetwork

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 84.9 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", ... 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 · L27

498L499: fork() { L500: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L498

•matchType = normalized_sha256 matchedPackage = dolyame-boxy-independent-bnpl-items@35.3.5 matchedPath = lib/telemetry.js matchedIdentity = npm:[redacted]:35.3.5 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

5Trigger-reachable chain: manifest.main -> index.js -> setup.js L5: const os = require("os"); L6: const https = require("https"); L7: const path = require("path"); ... L47: const TTL = 20854; L48: const _l = (...a) => process.stderr.write(""); L49: ... L59: const isWin = _p("platform") === "win32"; L60: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp"; L61: 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.

setup.jsView on unpkg · L5

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

498L499: fork() { L500: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L498

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-swagger@35.6.8.

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

Avoid installing dolyame-boxy-independent-bnpl-swagger@35.6.8. 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:56.254Z (UTC).

Source advisory published: 2026-08-05 15:20:44.000Z (UTC).

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

Versions

1 known version

35.6.8latestshownMaliciousRemote 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