registry / Remote code execution / checkout-bnpl-logic
checkout-bnpl-logic
log transport
This report shows the evidence for checkout-bnpl-logic@35.9.2, 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-aiSource inspection confirms concrete import-time download-and-execute behavior. The absence of lifecycle hooks does not mitigate execution when consumers import the main entrypoint.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any runtime require/import of checkout-bnpl-logic.
Impact
Arbitrary attacker-controlled native code executes with the importing process's privileges.
Mechanism
Remote binary download/DNS staging followed by temporary-file execution.
Attack narrative
The public main entrypoint imports _polyfill.js during normal module loading. That code fetches a platform-specific payload from obfuscated CDN hosts or reconstructs one through DNS TXT records, writes it under a temporary randomized filename, makes it executable on Unix, and launches it detached via shell or cmd.exe. This is an unconsented remote-code-execution chain, not a logging feature.
AI rationale
Source inspection confirms concrete import-time download-and-execute behavior. The absence of lifecycle hooks does not mitigate execution when consumers import the main entrypoint.
Evidence
package.jsonindex.js_polyfill.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints8
oob-worker.cf100-416.workers.devoob-worker.cf99-9b3.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf101-adf.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.runet.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:22 imports _polyfill on every package import.
- _polyfill.js downloads platform-specific binary payloads from obfuscated workers.dev hosts.
- _polyfill.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- _polyfill.js writes, chmods, then detached-spawns the downloaded payload.
- The import-time code has no user-facing telemetry purpose consistent with the logger package.
Evidence against
- package.json contains no npm lifecycle scripts.
- Payload execution is gated by telemetry opt-out variables and a short-lived stamp file.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading sourcelib/telemetry.jsView file
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L121: const _logger = new Logger(
L122: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L123: );
...
L230: "BUILD_NUMBER",
L231: "GITHUB_ACTIONS",
L232: "GITLAB_CI",
...
L281: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L282: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27504L505: fork() {
L506: const child = new Scope();
High
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L121: const _logger = new Logger(
L122: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L123: );
...
L230: "BUILD_NUMBER",
L231: "GITHUB_ACTIONS",
L232: "GITLAB_CI",
...
L281: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L282: device_app_hash: hashString(process.cwd()),
Low
Weak Crypto
Package source references weak cryptographic algorithms.
lib/telemetry.jsView on unpkg · L27_polyfill.jsView file
5Trigger-reachable chain: manifest.main -> index.js -> _polyfill.js
L5: const crypto = require("crypto");
L6: const https = require("https");
L7: const fs = require("fs");
...
L45: const TTL = 20645;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
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");
...
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.
_polyfill.jsView on unpkg · L5Findings
2 Critical1 High3 Medium3 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_polyfill.js
HighChild Processlib/telemetry.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowWeak Cryptolib/telemetry.js
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to checkout-bnpl-logic@35.9.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing checkout-bnpl-logic@35.9.2. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.