registry / Remote code execution / dolyame-boxy-atom-bnpl-info-card
dolyame-boxy-atom-bnpl-info-card
Internal dolyame boxy atom bnpl info card module for platform services
This report shows the evidence for dolyame-boxy-atom-bnpl-info-card@35.5.5. 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-aiThe import-time remote downloader/executor is concrete malicious behavior, not a package-aligned telemetry function. No lifecycle hook is needed because the public runtime entrypoint activates it.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Requiring/importing index.js at runtime
Impact
Arbitrary remote code execution under the consuming application's user account.
Mechanism
Remote payload download, drop, chmod, and detached execution
Attack narrative
A normal import of index.js silently requires _loader.js. Its immediately invoked run() fetches a platform payload from obfuscated workers.dev hosts, falling back to DNS TXT reconstruction from wel1.ru. It writes the payload to a temporary path, marks it executable on Unix, and launches it detached via a shell or cmd.exe. This creates unauthenticated remote code execution without any user action beyond importing the package.
AI rationale
The import-time remote downloader/executor is concrete malicious behavior, not a package-aligned telemetry function. No lifecycle hook is needed because the public runtime entrypoint activates it.
Evidence
package.jsonindex.js_loader.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%/analytics_state%TEMP%/dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/package
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 automatically on package import.
- _loader.js fetches platform-specific payloads from obfuscated workers.dev hosts.
- _loader.js also retrieves base64 payloads through DNS TXT records at wel1.ru subdomains.
- Downloaded data is written to /var/tmp or %TEMP%, made executable on Unix, then spawned detached.
- The loader suppresses errors and uses temporary marker files to limit repeat execution.
Evidence against
- package.json has no lifecycle scripts.
- lib/telemetry.js is not imported by the public entrypoint.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_loader.jsView file
4const os = require("os");
L5: const https = require("https");
L6: const fs = require("fs");
...
L44: const EXPIRE_SEC = 22474;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
L57: const isWin = _p("platform") === "win32";
L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L59: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_loader.jsView on unpkg · L44Trigger-reachable chain: manifest.main -> index.js -> _loader.js
L4: const os = require("os");
L5: const https = require("https");
L6: const fs = require("fs");
...
L44: const EXPIRE_SEC = 22474;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
L57: const isWin = _p("platform") === "win32";
L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L59: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: 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 · L4Findings
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-atom-bnpl-info-card@35.5.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-atom-bnpl-info-card@35.5.5. 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.