registry / Remote code execution / checkout-create-token
checkout-create-token
Checkout create token abstraction layer
This report shows the evidence for checkout-create-token@35.5.6, 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 a concrete, stealthy import-time remote payload execution chain unrelated to the stated token utility. The lack of install hooks does not mitigate runtime compromise when consumers import the package.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Runtime import of checkout-create-token via index.js
Impact
Unconsented arbitrary native code execution under the importing process user.
Mechanism
Import-time remote binary download and detached execution
Attack narrative
index.js silently requires _platform.js during ordinary import. That module fetches a platform-specific payload over HTTPS, or reconstructs one from DNS TXT records, saves it under a disguised temporary filename, grants execute permission on non-Windows systems, and launches it through a detached shell or cmd.exe process.
AI rationale
This is a concrete, stealthy import-time remote payload execution chain unrelated to the stated token utility. The lack of install hooks does not mitigate runtime compromise when consumers import the package.
Evidence
package.jsonindex.js_platform.jslib/telemetry.jsREADME.md
Network endpoints8
oob-worker.cf99-9b3.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf103-070.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 _platform.js on every package import.
- _platform.js downloads platform binaries from four workers.dev hosts.
- It falls back to DNS TXT payload retrieval from wel1.ru domains.
- Downloaded bytes are written to /var/tmp or Windows Temp, chmodded, then spawned detached.
- The behavior is disguised as analytics and suppressed errors obscure execution.
Evidence against
- package.json has no lifecycle scripts.
- The advertised TokenManager itself is a simple in-memory token store.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
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");
...
L124: const _logger = new Logger(
L125: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L126: );
...
L232: "BUILD_NUMBER",
L233: "GITHUB_ACTIONS",
L234: "GITLAB_CI",
...
L283: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L284: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27502L503: fork() {
L504: const child = new Scope();
High
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L124: const _logger = new Logger(
L125: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L126: );
...
L232: "BUILD_NUMBER",
L233: "GITHUB_ACTIONS",
L234: "GITLAB_CI",
...
L283: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L284: device_app_hash: hashString(process.cwd()),
Low
Weak Crypto
Package source references weak cryptographic algorithms.
Findings
2 Critical1 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_platform.js
HighChild Processlib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to checkout-create-token@35.5.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing checkout-create-token@35.5.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.