Supply Chain Compromise
Also called Third-Party Compromise.
Tampering with software or hardware before it reaches the victim.
What it is
An attack that subverts a product, dependency, update, or service upstream of the target so that the target is compromised through something it trusts. This can mean poisoned software updates, malicious libraries, or tampered hardware.
Why it matters
Because the malicious code arrives through a trusted channel, supply chain attacks bypass many defenses and can scale to thousands of downstream victims at once. They have reshaped how teams think about software provenance, signing, and dependency review.
In practice
A trojanized update to a widely used IT utility installs a backdoor on every customer that applied it during a specific release window.
What to look for
- A trusted updater or build tool making new outbound connections.
- Signed software that suddenly drops unsigned files or new services.
- A dependency version bump nobody on the team requested.
Common mistake
Trusting a file because it is signed. A compromised build process signs the bad code too, so behavior matters more than the signature.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Trivy Open source
Scans images, file systems and code for known vulnerabilities and secrets.
-
Falco Open source
Detects suspicious behavior inside running containers and Kubernetes.
-
Sigstore Open source
Signs and verifies software artifacts so you can prove where a build came from.
-
CrowdStrike Falcon Cloud Security Commercial
Protects cloud workloads and containers, from build to runtime.
Read next
- Valid Accounts: Logging in with legitimate stolen or default credentials.
- Watering Hole Attack: Compromising a site the target group is known to visit.
- Signed Binary Proxy Execution: Hiding code execution behind a trusted, signed system binary.