registry / Remote code execution / checkout-total-logic
checkout-total-logic
log transport
This report shows the evidence for checkout-total-logic@35.8.3, 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-aiDirect source inspection confirms an import-time remote payload execution chain, not merely telemetry primitives. The absence of npm lifecycle hooks does not mitigate execution on normal package use.
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-total-logic.
Impact
Arbitrary code execution under the importing process user.
Mechanism
remote binary download, temp-file drop, chmod, and detached shell execution
Attack narrative
The package entrypoint silently loads _platform.js. That module immediately downloads opaque content from obfuscated worker hosts, falls back to DNS TXT payload reconstruction, writes the content as a temporary executable, marks it executable on Unix, and runs it detached through a shell or cmd.exe. This is a concrete remote-code-execution chain activated by a normal import.
AI rationale
Direct source inspection confirms an import-time remote payload execution chain, not merely telemetry primitives. The absence of npm lifecycle hooks does not mitigate execution on normal package use.
Evidence
package.jsonindex.js_platform.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.cf100-416.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf102-baf.workers.dev/pkg/packagesdk.dl.wel1.ruext.dl.wel1.rupkg.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 fetches executable-sized bytes from worker hosts or DNS TXT.
- _platform.js writes payloads to /var/tmp or Windows Temp, chmods them, then spawns them.
- The payload runner is automatic at import time; no user setup API is required.
- lib/telemetry.js independently implements the same download-to-temp-and-execute pattern.
Evidence against
- package.json has no lifecycle scripts.
- The main exported Logger itself is simple console logging.
- Opt-out environment checks exist but do not make execution user-invoked.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
5 flagged · loading sourcelib/telemetry.jsView file
27L28: const https = require("https");
L29: const dns = require("dns");
L30: const fs = require("fs");
...
L116: const _logger = new Logger(
L117: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L118: );
...
L224: "BUILD_NUMBER",
L225: "GITHUB_ACTIONS",
L226: "GITLAB_CI",
...
L275: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L276: device_app_hash: hashString(process.cwd()),
Critical
Download Execute
Source downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27494L495: fork() {
L496: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = checkout-context@35.5.4
matchedPath = lib/telemetry.js
matchedIdentity = npm:Y2hlY2tvdXQtY29udGV4dA:35.5.4
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/telemetry.jsFindings
2 Critical2 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_platform.js
HighChild Processlib/telemetry.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowWeak Cryptolib/telemetry.js
LowFilesystem
Affected versions and remediation
This report applies to checkout-total-logic@35.8.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing checkout-total-logic@35.8.3. 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.