registry / Remote code execution / checkout-use-notifications
checkout-use-notifications
Checkout use notifications runtime support module
This report shows the evidence for checkout-use-notifications@35.6.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-aiThe manifest has no install hook, but normal runtime import immediately reaches a concealed remote binary loader and detached executor. This is concrete malware behavior, not package-aligned notification functionality.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Runtime import/require of checkout-use-notifications.
Impact
Unconsented remote code execution under the importing process user.
Mechanism
remote payload download, drop, and detached execution
Attack narrative
At import time, index.js loads _shim.js. The shim selects an OS payload endpoint, downloads bytes from rotating Workers hosts or reconstructs them from DNS TXT records, writes the result to a temporary executable path, and launches it detached via cmd.exe or /bin/sh. The network and process failures are swallowed, while a stamp file limits repeat attempts.
AI rationale
The manifest has no install hook, but normal runtime import immediately reaches a concealed remote binary loader and detached executor. This is concrete malware behavior, not package-aligned notification functionality.
Evidence
package.jsonindex.js_shim.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packagec.sdk.dl.wel1.ruc.ext.dl.wel1.ruc.pkg.dl.wel1.ruc.net.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 _shim.js on every package import.
- _shim.js downloads platform payloads, including DNS TXT fallback.
- _shim.js writes payloads to temp storage, chmods Unix files, and detached-spawns them.
- Execution is silently suppressed and throttled with a temporary stamp file.
Evidence against
- package.json has no lifecycle scripts.
- No credential or environment-value exfiltration was found; env vars only control opt-out/temp paths.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
3 flagged · loading source_shim.jsView file
5const path = require("path");
L6: const https = require("https");
L7: const fs = require("fs");
...
L45: const EXPIRE_SEC = 21730;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: if (e || !rr || !rr.length) return r("");
Critical
5Trigger-reachable chain: manifest.main -> index.js -> _shim.js
L5: const path = require("path");
L6: const https = require("https");
L7: const fs = require("fs");
...
L45: const EXPIRE_SEC = 21730;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L58: const isWin = _p("platform") === "win32";
L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L60: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: 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.
_shim.jsView on unpkg · L5Findings
2 Critical1 High2 Medium1 Low
CriticalDownload Execute_shim.js
CriticalTrigger Reachable Dangerous Capability_shim.js
HighChild Process_shim.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to checkout-use-notifications@35.6.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing checkout-use-notifications@35.6.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.