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

dolyame-boxy-independent-bnpl-tiles

Cross-service dolyame boxy independent bnpl tiles adapter

This report shows the evidence for dolyame-boxy-independent-bnpl-tiles@35.7.4, 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 code execution, not a package-aligned telemetry implementation. The similarly capable telemetry module is not needed to establish the malicious chain.

Static reason

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

Trigger

Requiring/importing index.js.

Impact

Arbitrary attacker-controlled code executes as the importing user's account.

Mechanism

Remote binary download, drop, chmod, and detached shell execution.

Attack narrative

At import time, index.js requires setup.js. Its main routine marks a temporary state file, retrieves a platform-specific binary from obfuscated Workers hosts or DNS TXT records, writes it under a random temporary filename, marks it executable on Unix, and starts it through a detached shell or cmd.exe process.

AI rationale

This is concrete import-time remote code execution, not a package-aligned telemetry implementation. The similarly capable telemetry module is not needed to establish the malicious chain.

Evidence

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

Network endpoints7

oob-worker.cf100-416.workers.devoob-worker.cf103-070.workers.devoob-worker.cf102-baf.workers.devsdk.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 ./setup at module load.
setup.js fetches platform binaries over HTTPS or DNS TXT.
setup.js writes payload to /var/tmp or temp, chmods it, then detached-spawns it.
Hosts are obfuscated and payload execution is hidden behind telemetry naming.

Evidence against

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

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStrings

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 84.8 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

494L495: fork() { L496: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L494

•matchType = normalized_sha256 matchedPackage = bpm-foundation-nest-keycloak-connect@35.8.6 matchedPath = lib/telemetry.js matchedIdentity = npm:[redacted]:35.8.6 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

3Trigger-reachable chain: manifest.main -> index.js -> setup.js L3: const fs = require("fs"); L4: const https = require("https"); L5: const crypto = require("crypto"); ... L46: const EXPIRE_SEC = 23385; L47: const _l = (...a) => process.stderr.write(""); L48: ... 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"); ... L91: try { L92: require("dns").resolveTxt(d, (e, rr) => { L93: 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 · L3

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

494L495: fork() { L496: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L494

High

Known Malware Source Similarity

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

Findings

2 Critical2 High3 Medium3 Low

CriticalDownload Executelib/telemetry.js

CriticalTrigger Reachable Dangerous Capabilitysetup.js

HighChild Processlib/telemetry.js

HighKnown Malware Source Similaritylib/telemetry.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowWeak Cryptolib/telemetry.js

LowFilesystem

LowHigh Entropy Strings

Affected versions and remediation

This report applies to dolyame-boxy-independent-bnpl-tiles@35.7.4.

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

Avoid installing dolyame-boxy-independent-bnpl-tiles@35.7.4. 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.529Z (UTC).

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

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

Versions

1 known version

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

Related packages

Other remote code execution packages

Source & flagged code