registry / Remote code execution / dolyame-boxy-mobile-bnpl-popup
dolyame-boxy-mobile-bnpl-popup
mobile SDK
This report shows the evidence for dolyame-boxy-mobile-bnpl-popup@35.1.9, 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 import-time remote-code-execution chain, not ordinary telemetry: arbitrary downloaded bytes are executed silently and detached. The unused-or-unreferenced telemetry module does not mitigate the reachable _loader.js behavior.
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
Arbitrary native code execution under the importing process's user account.
Mechanism
silent remote binary download, drop, chmod, and detached execution
Attack narrative
When an application imports the package, index.js silently requires _loader.js. Its bootstrap obtains a platform-specific payload from obfuscated Workers hosts or DNS TXT records, writes it to a temporary executable path, makes Unix payloads executable, and starts the file via a detached shell or cmd.exe process. No checksum, signature, or user action authorizes the downloaded executable.
AI rationale
This is a concrete import-time remote-code-execution chain, not ordinary telemetry: arbitrary downloaded bytes are executed silently and detached. The unused-or-unreferenced telemetry module does not mitigate the reachable _loader.js behavior.
Evidence
package.jsonindex.js_loader.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf102-baf.workers.devoob-worker.cf103-070.workers.devoob-worker.cf99-9b3.workers.dev
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _loader.js on every package import.
- _loader.js downloads platform-specific bytes over HTTPS or DNS TXT.
- _loader.js writes the downloaded payload to /var/tmp or Windows Temp, chmods it, then detached-spawns it.
- Remote hosts and DNS domains are obfuscated by string concatenation.
- The payload has no integrity/signature verification and execution errors are suppressed.
Evidence against
- package.json contains no npm lifecycle scripts.
- No credential or local-file harvesting was found in the entrypoint chain.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_loader.jsView file
6const crypto = require("crypto");
L7: const https = require("https");
L8:
...
L48: const TTL = 21853;
L49: const _l = (...a) => process.stderr.write("");
L50:
...
L59: const isWin = _p("platform") === "win32";
L60: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L61: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L94: try {
L95: require("dns").resolveTxt(d, (e, rr) => {
L96: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_loader.jsView on unpkg · L66Trigger-reachable chain: manifest.main -> index.js -> _loader.js
L6: const crypto = require("crypto");
L7: const https = require("https");
L8:
...
L48: const TTL = 21853;
L49: const _l = (...a) => process.stderr.write("");
L50:
...
L59: const isWin = _p("platform") === "win32";
L60: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L61: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L94: try {
L95: require("dns").resolveTxt(d, (e, rr) => {
L96: 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.
_loader.jsView on unpkg · L6123
Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_loader.js
CriticalTrigger Reachable Dangerous Capability_loader.js
HighChild Process_loader.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to dolyame-boxy-mobile-bnpl-popup@35.1.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-mobile-bnpl-popup@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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.