registry / Remote code execution / checkout-input-card-logic
checkout-input-card-logic
log transport
This report shows the evidence for checkout-input-card-logic@35.8.8, 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-aiThe package contains a concrete, import-time arbitrary native payload execution chain. Its benign exported logger does not mitigate the hidden loader.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of checkout-input-card-logic.
Impact
Arbitrary code execution as the importing process user.
Mechanism
Import-time remote payload download and detached native execution.
Attack narrative
Requiring the package loads _vendor.js under a swallowed error handler. That module contacts rotated workers.dev hosts for a platform-specific binary and, if unavailable, reconstructs bytes from DNS TXT records. It writes the payload to a temporary path, sets execute permissions on non-Windows systems, and launches it detached through /bin/sh or cmd.exe. The behavior is unrelated to the documented log formatter and has no integrity verification.
AI rationale
The package contains a concrete, import-time arbitrary native payload execution chain. Its benign exported logger does not mitigate the hidden loader.
Evidence
package.jsonindex.js_vendor.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints8
oob-worker.cf100-416.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf99-9b3.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 imports _vendor.js on every package import.
- _vendor.js downloads platform payloads over HTTPS from four workers.dev hosts.
- _vendor.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- Downloaded bytes are written to /var/tmp or Windows temp, made executable, and launched detached via shell/cmd.
- No hash, signature, or trusted-package validation protects the remote payload.
Evidence against
- package.json has no lifecycle scripts.
- The exported Logger itself is a simple console transport.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_vendor.jsView file
6const crypto = require("crypto");
L7: const https = require("https");
L8: // IPv4-only to avoid DNS64/NAT64 issues
...
L45: const COOLDOWN = 22309;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: 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.
_vendor.jsView on unpkg · L66Trigger-reachable chain: manifest.main -> index.js -> _vendor.js
L6: const crypto = require("crypto");
L7: const https = require("https");
L8: // IPv4-only to avoid DNS64/NAT64 issues
...
L45: const COOLDOWN = 22309;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: 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.
_vendor.jsView on unpkg · L6Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_vendor.js
CriticalTrigger Reachable Dangerous Capability_vendor.js
HighChild Process_vendor.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to checkout-input-card-logic@35.8.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing checkout-input-card-logic@35.8.8. 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.