Threat Detection

The supply-chain attack conditions Chainsaw detects on the install path — malware, typosquats, dependency confusion, behavioral and payload signals — plus the trust score that ties them together.

How to Detect Known Malware in Your Supply Chain Understand Chainsaw's malware index powered by OpenSSF data, review malware detections, and configure automatic blocking of malicious packages. Intermediate 20 minutes Security Engineers How to Detect and Prevent Typosquatting Attacks Understand Chainsaw's BK-tree typosquat detection, review flagged packages, and create policies that block suspected typosquats. Intermediate 20 minutes Security Engineers How to Protect Against Dependency Confusion Attacks Configure reserved namespace policies and internal package flags to prevent attackers from hijacking your private package names on public registries. Advanced 20 minutes Security Engineers / DevOps Engineers How to Apply Reserved-Namespace Starter Packs Turn on one-click dependency-confusion protection with the curated reserved-namespace packs shipped in configs/reserved_namespaces_defaults.yaml. Beginner 10 minutes Security Engineers / Platform Engineers How to Detect Install-Script Exfiltration Block PhantomRaven-style dynamic install dependencies and obfuscated eval(atob(...)) payloads with the hasInstallScript and installScriptFetchesRemote conditions. Intermediate 15 minutes Security Engineers How to Detect Compromised Packages with publisherChanged and versionAnomaly Catch Axios-style maintainer-takeover drops, semver regressions, multi-major skips, and backdated publishes before they reach your builds. Intermediate 20 minutes Security Engineers How to Detect Hidden Unicode Payloads (GlassWorm / Trojan Source) Block packages carrying zero-width, bidi-override, or Unicode-tag payloads with the hasHiddenUnicode condition. Intermediate 10 minutes Security Engineers How to Detect Shai-Hulud-Style Worm Bursts Catch attackers auto-publishing hundreds of packages from a compromised token with the publishVelocityAnomaly condition. Intermediate 15 minutes Security Engineers How to Scan Container Image Layers and the Docker Malware Feed Catch vulnerabilities hidden beneath a clean manifest with per-layer Trivy scanning, and close the OpenSSF index gap for containers with the Docker-specific feed. Advanced 20 minutes Platform Engineers / Security Engineers How to Detect Bypass Attempts with `chainsaw doctor --bypass-check` Find clients that are still reaching the public registries directly — the proxy is in place, but did everyone actually point at it? Two complementary surfaces: the doctor command from each client, and the `direct_registry_egress` view from the control plane. Intermediate 20 minutes Security Engineers / Platform Engineers How to Use Trust Scores to Assess Package Risk Understand the 0-100 composite trust score breakdown, filter by trust score, and build policies around package trust levels. Intermediate 20 minutes Security Engineers / Compliance Teams

These are the conditions Chainsaw evaluates for every package — the attacks it recognizes on the install path. Each one is usable in a policy (see Policy & Enforcement) to refuse, quarantine, or notify. The guides below split into two clusters — classic name/namespace attacks (malware, typosquats, dependency confusion) and behavioral or payload signals (install-script exfil, maintainer takeovers, hidden Unicode, publish-velocity bursts, container layers) — plus bypass detection and the trust score that aggregates them.

Start with the trust score. The composite 0–100 trust score rolls the signals below into one number you can gate on. Read it first to understand how the individual signals combine.

Where to next

Turn any condition into an enforced rule in Policy & Enforcement. Model-specific threats (pickle opcodes, prompt injection) live in AI/ML Supply Chain.