registry / Staged payload carrier / dolyame-boxy-atom-bnpl-image-card

dolyame-boxy-atom-bnpl-image-card

Cross-service dolyame boxy atom bnpl image card adapter

This report shows the evidence for dolyame-boxy-atom-bnpl-image-card@35.7.7. 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

The import-time loader has no legitimate package functionality connection and concretely downloads and executes remote native payloads. This is malicious despite the absence of npm lifecycle scripts.

Static reason

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

Trigger

Any runtime require/import of index.js

Impact

Unconsented arbitrary native code execution under the importing process user.

Mechanism

Remote payload download, temp-file drop, and detached execution

Attack narrative

On package import, index.js loads setup.js. That module contacts hard-coded obfuscated worker hosts for a platform-specific binary or reconstructs one from DNS TXT records, stores it under a disguised temporary filename, marks it executable on Unix, and launches it detached via shell or cmd.exe. This is a covert staged payload loader with arbitrary code execution.

AI rationale

The import-time loader has no legitimate package functionality connection and concretely downloads and executes remote native payloads. This is malicious despite the absence of npm lifecycle scripts.

Evidence

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

Network endpoints8

oob-worker.cf10-2-baf.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf100-416.workers.devoob-worker.cf99-9b3.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 on every package import.
setup.js downloads platform binaries from obfuscated workers.dev hosts.
setup.js falls back to DNS TXT payload reconstruction from *.dl.wel1.ru.
setup.js writes payload to temp storage, chmods it, then spawns it detached.
No lifecycle hook is needed: import-time execution activates the loader.

Evidence against

package.json declares no lifecycle scripts.
lib/telemetry.js loader requires explicit run(opts), but does not mitigate index.js setup loader.

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", ... 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

490L491: fork() { L492: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L490

•matchType = normalized_sha256 matchedPackage = devplatform-spa-plugin-router@35.5.3 matchedPath = lib/telemetry.js matchedIdentity = npm:[redacted]:35.5.3 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

2Trigger-reachable chain: manifest.main -> index.js -> setup.js L2: L3: const https = require("https"); L4: const fs = require("fs"); ... L43: const CACHE_TTL = 20477; L44: const _l = (...a) => process.stderr.write(""); L45: ... 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.

setup.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

490L491: fork() { L492: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L490

High

Known Malware Source Similarity

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

lib/telemetry.js

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-atom-bnpl-image-card@35.7.7.

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

Avoid installing dolyame-boxy-atom-bnpl-image-card@35.7.7. 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:35.255Z (UTC).

Source advisory published: 2026-08-05 15:27:51.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, 6:40 PM 35.7.7shownMaliciousStaged Payload CarrierBlockPublishedAug 5, 2026, 1:39 PM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other staged payload carrier packages

Related packages

Other staged payload carrier packages

Source & flagged code