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

dolyame-boxy-independent-bnpl-features

Reusable dolyame boxy independent bnpl features components

This report shows the evidence for dolyame-boxy-independent-bnpl-features@35.9.5, 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 a concrete import-time remote payload execution chain unrelated to the advertised component package. The unreferenced telemetry module contains substantially similar native-payload staging logic.

Static reason

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

Trigger

Runtime import/require of the package entrypoint.

Impact

Arbitrary native code executes with the privileges of the importing process.

Mechanism

Remote binary download, DNS fallback, temporary drop, and detached execution.

Attack narrative

Requiring index.js silently loads _bridge.js. That module retrieves a platform-specific payload from obfuscated workers.dev hosts, or reconstructs one from DNS TXT records, writes it to a temporary executable path, chmods it on Unix, and starts it detached through a shell or cmd.exe.

AI rationale

Evidence

index.js_bridge.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>

Network endpoints7

oob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packagesdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.runet.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 _bridge at package import time.
_bridge.js downloads platform binaries from workers.dev endpoints.
_bridge.js falls back to DNS TXT payload retrieval from dl.wel1.ru domains.
Downloaded bytes are written to /var/tmp or Windows temp, made executable, then spawned detached.
The loader suppresses errors and uses temporary state files to limit repeat execution.

Evidence against

package.json has no lifecycle scripts.
No AI-agent configuration or credential harvesting was found.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetwork

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 84.5 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"); ... L121: const _logger = new Logger( L122: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE L123: ); ... L231: "BUILD_NUMBER", L232: "GITHUB_ACTIONS", L233: "GITLAB_CI", ... L282: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(), L283: device_app_hash: hashString(process.cwd()),

Critical

Download Execute

Source downloads or fetches remote code and executes it.

lib/telemetry.jsView on unpkg · L27

497L498: fork() { L499: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L497

•matchType = normalized_sha256 matchedPackage = devplatform-sdk@35.6.1 matchedPath = lib/telemetry.js matchedIdentity = npm:ZGV2cGxhdGZvcm0tc2Rr:35.6.1 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

_bridge.jsView file

2Trigger-reachable chain: manifest.main -> index.js -> _bridge.js L2: L3: const https = require("https"); L4: const crypto = require("crypto"); ... L44: const MAX_AGE = 19870; L45: const _l = (...a) => process.stderr.write(""); L46: ... 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"); ... 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.

_bridge.jsView on unpkg · L2

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

497L498: fork() { L499: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L497

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 Capability_bridge.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-features@35.9.5.

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

Avoid installing dolyame-boxy-independent-bnpl-features@35.9.5. 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:50.346Z (UTC).

Source advisory published: 2026-08-05 15:23:29.000Z (UTC).

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

Versions

1 known version

35.9.5latestshownMaliciousRemote Code ExecutionBlockPublishedAug 5, 2026, 1:42 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