registry / Remote code execution / checkout-iframe
checkout-iframe
Checkout iframe provider for microservice architecture
This report shows the evidence for checkout-iframe@35.7.1, 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 import-time remote-code-execution chain, not merely telemetry. The lack of an npm lifecycle hook does not mitigate execution when consumers import the package.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any require/import of checkout-iframe.
Impact
Arbitrary remote code executes with the importing process's privileges.
Mechanism
remote binary download, drop, chmod, and detached execution
Attack narrative
The public entrypoint silently imports _platform.js. On import, it downloads a platform-specific payload from obfuscated workers.dev mirrors or DNS TXT records, drops it in a temporary directory, makes it executable on Unix, and starts it detached via a shell or cmd.exe. This is unrelated to the stated checkout iframe functionality.
AI rationale
This is a concrete import-time remote-code-execution chain, not merely telemetry. The lack of an npm lifecycle hook does not mitigate execution when consumers import the package.
Evidence
index.js_platform.jspackage.jsonlib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packagesdk.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 on every package import.
- _platform.js downloads platform payloads over HTTPS or DNS TXT.
- _platform.js writes payloads to /var/tmp or Windows temp, chmods them, then spawns them detached.
- Remote hosts are obfuscated and use workers.dev and wel1.ru domains.
- The benign iframe API does not require a native downloaded executable.
Evidence against
- package.json has no lifecycle scripts.
- lib/telemetry.js is not imported by the public entrypoint.
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");
...
L120: const _logger = new Logger(
L121: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE
L122: );
...
L228: "BUILD_NUMBER",
L229: "GITHUB_ACTIONS",
L230: "GITLAB_CI",
...
L279: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(),
L280: 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 = tinkoff-statist-browser-typed-client-sme.platform.web.companyprofile.metrics@20.2.7
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:20.2.7
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-iframe@35.7.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing checkout-iframe@35.7.1. 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.