registry / Remote code execution / checkout-use-toasts
checkout-use-toasts
Pluggable checkout use toasts interface
This report shows the evidence for checkout-use-toasts@35.3.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 concrete import-time remote payload execution unrelated to the declared toast interface. The absence of lifecycle hooks does not mitigate the reachable import trigger.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Runtime import of checkout-use-toasts.
Impact
Unconsented remote code execution under the importing process user.
Mechanism
obfuscated remote binary download and detached execution
Attack narrative
On import, index.js silently requires _bridge.js. Its bootstrapper fetches a platform-specific payload from obfuscated Worker hosts, falls back to DNS TXT payload retrieval, writes the bytes to a temp file, marks Unix files executable, and launches the file detached through a shell or cmd.exe.
AI rationale
This is concrete import-time remote payload execution unrelated to the declared toast interface. The absence of lifecycle hooks does not mitigate the reachable import trigger.
Evidence
package.jsonindex.js_bridge.jslib/telemetry.js
Network endpoints8
oob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf100-416.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 _bridge.js on every package import.
- _bridge.js immediately invokes bootstrap().
- _bridge.js downloads platform payloads from worker hosts or DNS TXT.
- _bridge.js writes, chmods, and detached-spawns the downloaded payload.
- Remote hosts and resolver domains are obfuscated by string concatenation.
Evidence against
- package.json has no lifecycle scripts.
- The documented toast API itself is minimal.
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 = tramvai-module-feature-toggle@20.5.3
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:20.5.3
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_bridge.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-use-toasts@35.3.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing checkout-use-toasts@35.3.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.