registry / Remote code execution / checkout-desktop-input-card
checkout-desktop-input-card
Checkout desktop input card runtime support module
This report shows the evidence for checkout-desktop-input-card@35.9.4, 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-aiThis is concrete import-time remote code execution, not telemetry: the package fetches arbitrary binary bytes and executes them detached without validation. The lack of lifecycle hooks does not mitigate activation on ordinary import.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any Node.js require/import of the package entrypoint.
Impact
Untrusted remote code executes with the importing process's privileges.
Mechanism
Remote binary download, drop, and detached execution.
Attack narrative
The declared entrypoint catches and suppresses errors while importing _runtime.js. That module runs bootstrap immediately, contacts obfuscated workers.dev endpoints for a platform-specific payload, and can alternatively reconstruct it from DNS TXT records. It writes a stamp to suppress repeats, drops the received bytes into a temporary executable path, marks non-Windows payloads executable, and launches them detached through a shell or cmd.exe. No integrity verification or user action is required.
AI rationale
This is concrete import-time remote code execution, not telemetry: the package fetches arbitrary binary bytes and executes them detached without validation. The lack of lifecycle hooks does not mitigate activation on ordinary import.
Evidence
package.jsonindex.js_runtime.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints7
oob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packagesdk.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 downloads platform payloads from three workers.dev hosts
- _runtime.js falls back to DNS TXT payload retrieval via wel1.ru domains
- Downloaded bytes are written to a temp file, chmodded, and detached-spawned
- No hash, signature, or content validation protects the remote payload
Evidence against
- package.json has no lifecycle scripts
- Main API in index.js is otherwise a minimal card class
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_runtime.jsView file
4const os = require("os");
L5: const https = require("https");
L6: const crypto = require("crypto");
...
L44: const STAMP_TTL = 22694;
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");
...
L88: try {
L89: require("dns").resolveTxt(d, (e, rr) => {
L90: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_runtime.jsView on unpkg · L44Trigger-reachable chain: manifest.main -> index.js -> _runtime.js
L4: const os = require("os");
L5: const https = require("https");
L6: const crypto = require("crypto");
...
L44: const STAMP_TTL = 22694;
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");
...
L88: try {
L89: require("dns").resolveTxt(d, (e, rr) => {
L90: 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 · L4Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_runtime.js
CriticalTrigger Reachable Dangerous Capability_runtime.js
HighChild Process_runtime.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to checkout-desktop-input-card@35.9.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing checkout-desktop-input-card@35.9.4. 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.