Quick answer
A supply chain attack compromises an organisation through a trusted supplier: a software update, a code library, a managed service provider or a vendor with access to your systems or data. One compromise upstream can reach thousands of downstream victims at once.
On this page
How It Works
Attackers target the supplier because it is a multiplier. Examples include malicious code inserted into legitimate software updates, poisoned open-source packages, stolen MSP remote management credentials used to push ransomware to clients, and mass exploitation of a file transfer product used by hundreds of organisations. AI coding assistants add a new variant: suggested packages that do not exist and are registered by attackers. See AI coding assistant security.
Why It Matters
You inherit your suppliers' security. Vendors often hold privileged, always-on access that bypasses your own controls, and incidents at a supplier can trigger your own notification obligations.
How to Test for It
- Inventory suppliers with network access, remote management tools or your data.
- Test what a compromised supplier account or remote management tool could reach in your environment.
- Review software dependencies for known vulnerabilities and suspicious packages.
- Check that third-party access uses MFA, least privilege and logging.
- Assess contractual security requirements and incident notification terms.
How to Reduce the Risk
Limit supplier access to what is needed and when it is needed, require MFA and logging, monitor remote management tools, maintain a software bill of materials, verify software updates where possible and include suppliers in incident response planning.
Regulatory and Framework Context
For Australian organisations, supply chain risk is a growing focus for ASD, APRA CPS 230 (operational risk, including material service providers) and the SOCI Act.
Being exploited now
Threat Radar →The latest related vulnerabilities confirmed as exploited in the wild.
- CVE-2026-97229·3 weeks ago·Dev toolsGitLab Community Edition and Enterprise EditionGitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound VulnerabilityEPSS 69.3%
- CVE-2026-102764·5 weeks ago·Remote mgmtBeyondTrust Remote SupportBeyondTrust Remote Support Authentication Bypass by Spoofing VulnerabilityEPSS 79.5%
- CVE-2026-21589·5 weeks ago·Dev toolsAtlassian Multiple ProductsAtlassian Multiple Products Files or Directories Accessible to External Parties VulnerabilityEPSS 99.7%
- CVE-2026-102489·7 weeks ago·Dev toolsZammad GmbH ZammadZammad GmbH Zammad Session Fixation VulnerabilityEPSS 49.9%
Latest intel on this topic
- Borrowed Code, Real Consequences: What OPTIMJACK Teaches UsUnit 42 · 17 November 2026
- The US wants its quantum lead to turn into factories and supply chainsCyberScoop · 10 November 2026
- Why Europe's Freezer Hacks Spread So Far, So FastDark Reading · 6 November 2026
- The Noise Inside the Network: How an Unsophisticated Attack Exposed a Third-Party RiskUnit 42 · 13 October 2026
- Updated guidance on the 2026 Minimum Elements for a Software Bill of MaterialsASD's ACSC · 2 September 2026
Updated hourly from the daily briefing. More in data breaches in australia: the latest reports.
Common questions
What is an example of a software supply chain attack?
A trusted vendor's update mechanism or code repository is compromised so customers install malicious code believing it is legitimate.
How do we assess an MSP's security?
Ask how they protect remote management tools, enforce MFA, separate client environments and detect misuse, and test what their access could reach in your environment.
Change log
- 13 November 2026First published.