Supply Chain
Software Supply Chain Attacks: Malicious Packages, SBOMs and How to Trust What You Ship
Most of the code you ship was written by someone else. Attackers have noticed, and they are publishing it for you.
A modern application is mostly open-source dependencies, plus a build pipeline that pulls them in automatically. Attackers now target that chain directly: publishing look-alike packages, taking over maintainer accounts, poisoning build systems and slipping malicious code into trusted updates. Group-IB's 2026 threat report flags supply chain attacks as one of the top emerging global threats.
How supply chain attacks get in
- Typosquatting — a package named one letter away from a popular one.
- Dependency confusion — a public package with the same name as your internal one, which your build pulls by mistake.
- Account takeover of maintainers — a legitimate package suddenly ships a malicious version.
- Compromised CI/CD — leaked pipeline secrets let attackers alter what gets built and signed.
- Install scripts that run on developer laptops and steal tokens the moment a package is added.
Controls that work
| Control | Stops |
|---|---|
| SBOM for every release | Not knowing whether a new vulnerable or malicious package affects you |
| Pinned versions and lockfiles, with review of new dependencies | Silent malicious updates |
| Private registry / proxy with allow-listing | Typosquats and dependency confusion |
| Least-privilege, short-lived CI credentials | Pipeline takeover |
| Artifact signing and provenance (SLSA) | Tampered builds reaching production |
SBOMs are also becoming a legal expectation: the EU Cyber Resilience Act's vulnerability handling depends on manufacturers knowing their components, and many enterprise buyers now ask for one in procurement.
Review your pipeline before an attacker does
We assess CI/CD pipelines, dependency hygiene and source code for supply chain weaknesses.
Explore source code & DevSecOps reviewFrequently asked questions
What is an SBOM?
A software bill of materials is a list of all components and dependencies in a piece of software, with versions, used to track vulnerabilities and licences.
What is dependency confusion?
An attack where a malicious public package uses the same name as a company's internal package, so build tools download the attacker's version instead.
What is SLSA?
Supply-chain Levels for Software Artifacts is a framework of controls for build integrity and provenance, so you can verify how and where software was built.
PITOWINGS Research
OSCP, CEH and ECES certified testers, SOC analysts and certified forensic investigators at PITOWINGS.
Keep reading
All articlesPITOWINGS · Insights
AI Security
11 min read
Agentic AI Security in 2026: Prompt Injection, MCP Servers and the OWASP Agentic Top 10
AI agents now read email, call APIs and change records on their own. The attack surface is no longer the prompt; it is everything the agent can see, call and remember.
PITOWINGS · Insights
Cryptography
10 min read
NIST IR 8547 Is Final: RSA and ECC Deprecated After 2030 — Your Post-Quantum Migration Plan
The quantum deadline now has a date on it. Here is what NIST's final transition plan changes, and a practical migration path that starts with knowing where your cryptography is.
PITOWINGS · Insights
Security Operations
9 min read
AI in the SOC: What AI Agents Can and Cannot Do for Threat Detection in 2026
AI can read every alert. It still cannot decide, on its own, whether to take your payment system offline at 3 a.m.


