Supply-Chain Implant
Also called Supply chain backdoor.
Malicious code slipped into trusted software before it ships.
What it is
A supply-chain implant is malicious functionality inserted into legitimate software, an update, or a dependency before it reaches victims, so the trusted distribution channel itself delivers the compromise. The carrier looks and is genuinely signed.
Why it matters
Because the malicious code arrives through software organizations already trust, it bypasses normal vetting and can reach many victims at once, making detection and scoping unusually hard. Comparing a build against expected source is often the only tell.
In practice
A signed software update carrying a hidden backdoor that activates only on a subset of victims days after installation.
What to look for
- Trusted software calling out to new domains.
- Updates signed correctly but behaving differently.
- Build systems or dependencies changed recently.
Common mistake
Trusting the vendor's signature. A compromised build signs the implant too.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Map and Score
Map real procedures to ATT&CK techniques, then pick the CVSS v3.1 metrics for real vulnerabilities.
- Linux Persistence Reader
Read a crontab line, a systemd unit or an auditd record, and see what runs, when, and as whom.
- Linux Case
A server making outbound connections nobody can explain: read its audit log, journal and scheduled jobs, and say who did what.
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
- Loader: Code that prepares and executes a payload, often only in memory.
- TTP Mapping: Translating observed malware behavior into named adversary techniques.
- Persistence Mechanism: The means malware uses to survive reboots and keep running.