registry / Remote code execution / dolyame-boxy-independent-bnpl-button
dolyame-boxy-independent-bnpl-button
Lightweight dolyame boxy independent bnpl button wrapper
This report shows the evidence for dolyame-boxy-independent-bnpl-button@35.3.6. 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-aiThis is a concealed import-time remote code execution chain unrelated to the stated button-wrapper functionality. No install hook is needed because package consumption triggers the loader.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any require/import of index.js.
Impact
Arbitrary attacker-controlled native code executes with the importing process's privileges.
Mechanism
remote binary download/DNS staging followed by temp-file execution
Attack narrative
A normal import reaches _runtime.js. Unless opt-out variables or a recent marker suppress it, it obtains a platform payload over HTTPS from rotating hosts or reconstructs it from DNS TXT records, writes it under a randomized temporary filename, marks it executable on Unix, and launches it detached via /bin/sh or cmd.exe.
AI rationale
This is a concealed import-time remote code execution chain unrelated to the stated button-wrapper functionality. No install hook is needed because package consumption triggers the loader.
Evidence
package.jsonindex.js_runtime.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints8
oob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf102-baf.workers.dev/pkg/packagesdk.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 _runtime.js on every package import.
- _runtime.js fetches platform-specific binary payloads from rotating workers.dev hosts.
- _runtime.js falls back to DNS TXT payload retrieval from *.dl.wel1.ru.
- Downloaded bytes are written to a temp path, chmodded on Unix, then detached-spawned through a shell.
- A temp marker only rate-limits execution; it does not require user consent.
Evidence against
- package.json has no lifecycle scripts.
- The public wrapper class itself is inert; the malicious behavior is hidden in its import side effect.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_runtime.jsView file
3const fs = require("fs");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L44: const MAX_AGE = 20765;
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");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_runtime.jsView on unpkg · L33Trigger-reachable chain: manifest.main -> index.js -> _runtime.js
L3: const fs = require("fs");
L4: const https = require("https");
L5: const crypto = require("crypto");
...
L44: const MAX_AGE = 20765;
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");
...
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.
_runtime.jsView on unpkg · L3Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_runtime.js
CriticalTrigger Reachable Dangerous Capability_runtime.js
HighChild Process_runtime.js
HighKnown Malware Source Similarity_runtime.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to dolyame-boxy-independent-bnpl-button@35.3.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-boxy-independent-bnpl-button@35.3.6. 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.