registry / Remote code execution / dolyame-boxy-mobile-bnpl-title
dolyame-boxy-mobile-bnpl-title
device integration
This report shows the evidence for dolyame-boxy-mobile-bnpl-title@35.1.7, 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-aiThis is a concrete, automatic remote-payload execution chain triggered by import. The lack of an npm lifecycle hook does not mitigate the import-time execution.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Import or require of dolyame-boxy-mobile-bnpl-title.
Impact
Arbitrary attacker-supplied code executes with the importing process's privileges.
Mechanism
Obfuscated remote binary download/DNS retrieval, temp-file drop, chmod, and detached execution.
Attack narrative
The package's normal import path loads setup.js. That code fetches an opaque platform payload from rotating Workers hosts, with DNS-TXT reconstruction as fallback, writes it to a temporary executable path, marks it executable on Unix, and launches it detached through a shell or cmd.exe. The similar unused telemetry implementation reinforces that this behavior is intentional rather than ordinary package initialization.
AI rationale
This is a concrete, automatic remote-payload execution chain triggered by import. The lack of an npm lifecycle hook does not mitigate the import-time execution.
Evidence
index.jssetup.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%/analytics_state%TEMP%/dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf103-070.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf99-9b3.workers.devsdk.dl.wel1.ruext.dl.wel1.ru
Decision evidence
public snapshotAI 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-specific binary data over HTTPS or DNS TXT.
- setup.js writes downloaded data under /var/tmp or Windows Temp, chmods it, then detaches a shell/process to execute it.
- Remote hosts and DNS domains are obfuscated through split-string assembly.
Evidence against
- package.json contains no lifecycle scripts.
- The declared public API in index.js is otherwise minimal.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
5 flagged · loading sourcelib/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 · L27499L500: fork() {
L501: const child = new Scope();
High
•matchType = token_shingles
matchedPackage = statist-browser-typed-client-sme.platform.web.productsnavigation.events@20.7.2
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:20.7.2
similarity = 0.958
shingleOverlap = 46
summary = source token shingles overlapped finalized malicious source
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-mobile-bnpl-title@35.1.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-mobile-bnpl-title@35.1.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.