registry / Remote code execution / dolyame-boxy-atom-bnpl-button
dolyame-boxy-atom-bnpl-button
Dolyame boxy atom bnpl button provider for microservice architecture
This report shows the evidence for dolyame-boxy-atom-bnpl-button@35.8.3. 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 package has no install hook, but normal import triggers a stealthy downloader-executor. The remote payload is neither authenticated nor package-aligned.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
A consumer imports/requires the package.
Impact
Arbitrary code execution as the importing process user.
Mechanism
Import-time remote binary download and detached execution.
Attack narrative
The public entrypoint suppresses errors while importing _helpers.js. That module contacts hard-coded remote hosts for an opaque platform payload, falls back to DNS TXT chunking, saves any payload over 1000 bytes to a temporary executable file, and starts it detached via cmd.exe or /bin/sh. This is concrete, unconsented import-time remote code execution.
AI rationale
The package has no install hook, but normal import triggers a stealthy downloader-executor. The remote payload is neither authenticated nor package-aligned.
Evidence
package.jsonindex.js_helpers.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.cf101-adf.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf102-baf.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 _helpers.js on every package require.
- _helpers.js downloads platform binaries from four workers.dev hosts, with DNS TXT fallback via *.dl.wel1.ru.
- _helpers.js writes the downloaded payload to a temporary executable path, chmods it on Unix, then launches it detached through a shell.
- No payload signature or hash verification is implemented despite a comment claiming integrity checking.
Evidence against
- package.json has no lifecycle scripts.
- lib/telemetry.js is not imported by the package entrypoint.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_helpers.jsView file
6const os = require("os");
L7: const https = require("https");
L8:
...
L44: const MAX_AGE = 22004;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
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");
...
L93: try {
L94: require("dns").resolveTxt(d, (e, rr) => {
L95: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_helpers.jsView on unpkg · L66Trigger-reachable chain: manifest.main -> index.js -> _helpers.js
L6: const os = require("os");
L7: const https = require("https");
L8:
...
L44: const MAX_AGE = 22004;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
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");
...
L93: try {
L94: require("dns").resolveTxt(d, (e, rr) => {
L95: 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.
_helpers.jsView on unpkg · L6122
Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_helpers.js
CriticalTrigger Reachable Dangerous Capability_helpers.js
HighChild Process_helpers.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to dolyame-boxy-atom-bnpl-button@35.8.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-atom-bnpl-button@35.8.3. 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.