anydeskrce-something/03-supply-chain-social-engineering.md

# Supply Chain Social Engineering Attacks -- Defensive Analysis

## Table of Contents
1. [Trojanized Package Attacks](#1-trojanized-package-attacks)
2. [Compromised Software Update Mechanisms](#2-compromised-software-update-mechanisms)
3. [Fake Software Distribution Sites](#3-fake-software-distribution-sites)
4. [Gaming & Modding Community Attacks](#4-gaming--modding-community-attacks)
5. [Browser Extension Attacks](#5-browser-extension-attacks)
6. [Open Source Maintainer Compromise](#6-open-source-maintainer-compromise)
7. [Defensive Measures by Vector](#7-defensive-measures-by-vector)
8. [Key Metrics & Trends](#8-key-metrics--trends)

---

## 1. Trojanized Package Attacks

### Attack Vectors

**Typosquatting** -- Registering package names that are near-misspellings of popular packages. Attackers target developers who mistype `pip install` or `npm install` commands. In 2023, researchers documented a campaign registering 900 typosquats of 40 popular PyPI packages. By 2024, campaigns scaled to 500+ malicious packages published in single batches.

**Dependency Confusion** -- Exploiting package manager resolution behavior where a public package with a higher version number takes precedence over an internal/private package of the same name. NuGet is particularly vulnerable; Maven Central is less so due to strict group ID verification via DNS. Alex Birsan's original 2021 research demonstrated this against Apple, Microsoft, and PayPal.

**Account Compromise & Maintainer Takeover** -- Attackers phish or credential-stuff maintainer accounts, then push malicious updates to legitimate packages with large install bases.

**Protestware/Sabotage** -- Maintainers intentionally destroying or weaponizing their own packages.

### Notable Incidents

| Incident | Year | Ecosystem | Impact | Technique |
|----------|------|-----------|--------|-----------|
| **event-stream** | 2018 | npm | Bitcoin wallet theft via flatmap-stream dependency | Social engineering maintainer into transferring ownership to attacker "right9ctrl" |
| **ua-parser-js** | 2021 | npm | Crypto miners + password stealers pushed to 7M weekly downloads | Maintainer account compromise |
| **colors.js / faker.js** | 2022 | npm | Infinite loop bricking thousands of apps | Maintainer self-sabotage (protestware) |
| **node-ipc (peacenotwar)** | 2022 | npm | Recursive file overwrite on Russian/Belarusian IPs; affected Vue.js | Maintainer-injected protestware (CVE-2022-23812) |
| **ctx + phpass** | 2022 | PyPI/PHP | Credential theft | Expired maintainer domain re-registration |
| **MUT-8694** | 2024 | npm + PyPI | Cross-ecosystem credential harvesting on Windows | Coordinated typosquatting across two registries |
| **chalk / debug / ansi-regex** | Sep 2025 | npm | Crypto wallet hijacking via 18 popular libraries | Maintainer "qix" phished; obfuscated code injected |
| **September 2025 npm attack** | Sep 2025 | npm | 200+ packages compromised | Large-scale coordinated campaign; CISA advisory issued |
| **Beamglea** | Oct 2025 | npm | 175 malicious packages for credential harvesting | Bulk upload campaign identified by Socket |
| **Shai-Hulud v2** | Nov 2025 | npm + Maven | Credential breadth + destructive fallback behavior | Cross-ecosystem expansion with kill switches |
| **shanhai666 NuGet logic bombs** | 2023-2024 | NuGet | Industrial PLC sabotage (Sharp7Extend); trigger dates in 2027-2028 | Time-delayed logic bombs in 9 packages |

### Scale

- Malicious npm packages surged from 38 reports (2018) to 2,168 (2024). Snyk identified 3,000+ malicious npm packages in 2024 alone.
- Sonatype tracked 454,648 new malicious packages across npm, PyPI, Maven Central, and NuGet in a single year (2025 report).
- 156% year-over-year increase in malicious packages (Sonatype 2025).
- 15% of breaches now stem from supply chain attacks.
- Open source registries processed 9.8 trillion downloads across major ecosystems.

### Evasion Techniques

- **Delayed execution**: Malicious payloads activate only after a timer or specific trigger date
- **Remotely-controlled kill switches**: Fetch executable code at runtime from C2 servers
- **Install-time scripts**: `postinstall` hooks in npm, `setup.py` execution in PyPI
- **Obfuscated payloads**: Base64-encoded, string-split, or encrypted code blocks
- **Conditional activation**: Check for CI environment variables, geolocation, or specific hostnames before executing

---

## 2. Compromised Software Update Mechanisms

These represent the highest-impact supply chain attacks because they abuse the implicit trust users place in signed, official software updates.

### SolarWinds / SUNBURST (December 2020)

**Attack chain:**
1. Attackers (attributed to Russian SVR / APT29) infiltrated SolarWinds' build environment
2. Malicious code injected into the Orion platform's DLL (`SolarWinds.Orion.Core.BusinessLayer.dll`) *before* code signing
3. SolarWinds digitally signed the backdoored build -- the signature was legitimate
4. Trojanized updates distributed via normal update channel to ~18,000 organizations
5. Backdoor (SUNBURST) communicated via DNS to C2, with domain names generated from victim environment data
6. Secondary payloads (TEARDROP, Raindrop) deployed selectively against high-value targets

**Impact:** US Treasury, Commerce Department, DHS, DOJ, Fortune 500 companies. Estimated 100+ organizations actively exploited out of 18,000 infected.

**Key lesson:** Code signing alone is not a defense if the build pipeline is compromised. The signature validated that the code came from SolarWinds -- which it did, because the build system itself was owned.

### Kaseya VSA / REvil (July 2021)

**Attack chain:**
1. REvil ransomware gang exploited zero-day vulnerabilities in Kaseya's VSA (Virtual System Administrator) on-premises servers
2. VSA is used by Managed Service Providers (MSPs) to manage client endpoints
3. Attackers sent malicious updates through VSA to MSP client systems
4. 800-1,500 downstream businesses hit with ransomware through a small number of compromised MSPs

**Key lesson:** MSP/RMM tools are force multipliers -- compromising one MSP cascades to hundreds of endpoints. The trust model of remote management tools makes them ideal supply chain pivot points.

### Codecov Bash Uploader (January-April 2021)

**Attack chain:**
1. Attackers found credentials leaked via an error in Codecov's Docker image creation process
2. Used credentials to modify the Bash Uploader script hosted at `codecov.io/bash`
3. Modified script exfiltrated CI environment variables (secrets, tokens, API keys) from every CI pipeline using Codecov
4. Exfiltrated data sent to attacker-controlled server
5. Went undetected for ~3 months (Jan 31 - April 1, 2021)

**Key lesson:** CI/CD scripts fetched from remote URLs at build time are a single point of compromise. Any secrets in CI environment variables were exposed.

### 3CX Desktop App (March 2023)

**Attack chain:**
1. A 3CX developer installed a trojanized trading application (Trading Technologies X_TRADER)
2. That trojanized app stole the developer's credentials
3. Attackers used stolen credentials to access 3CX build environment
4. Malicious DLL (ffmpeg.dll) bundled into signed 3CX desktop client
5. Valid 3CX code-signing certificate used -- downloads came from official 3CX servers
6. Attribution: Lazarus Group (North Korea) -- a supply chain attack that originated from *another* supply chain attack

**Key lesson:** This was a chained supply chain attack -- Trading Technologies was compromised first, then used as a vector into 3CX. Attackers are now chaining compromises across organizations.

### Common Patterns Across All Four

1. **Legitimate signatures**: All attacks distributed code signed with valid certificates
2. **Build environment as target**: The build pipeline, not the source repository, was the point of injection
3. **Trust inheritance**: Downstream consumers trusted the update because the vendor's signing infrastructure said it was authentic
4. **Dwell time**: Weeks to months before detection (SolarWinds: ~9 months, Codecov: ~3 months)
5. **Selective targeting**: Sophisticated actors (SolarWinds, 3CX) used the broad compromise to selectively target high-value victims

---

## 3. Fake Software Distribution Sites

### SEO Poisoning Campaigns

Attackers create convincing clones of legitimate software download pages, then use SEO manipulation and/or paid Google Ads to rank them above or alongside official sites in search results.

**Scale (2024-2025):**
- A 15,000-site campaign discovered in 2024 compromised victims within days of going live
- PuTTY/WinSCP campaign reached 8,500+ infected IT administrator systems in under two weeks
- Campaigns target searchers for: OBS, Blender, VLC, 7-Zip, CCleaner, PuTTY, WinSCP, Notepad++, and other popular free tools

**Techniques:**
- **Google Ads abuse**: Purchasing ad placement for software names; malicious ads appear above organic results
- **SEO plugin manipulation**: Compromising legitimate sites and injecting SEO plugins to boost rankings
- **Lookalike domains**: Registering domains visually similar to official sites (e.g., `n0tepad-plus.com`)
- **Legitimate-looking landing pages**: Pixel-perfect clones of official download pages
- **Signed malware**: Some campaigns use stolen or purchased code-signing certificates

**Payloads commonly delivered:**
- Vidar info-stealer (via fake Blender/OBS downloads)
- IcedID/BokBot (via fake productivity software)
- Raccoon Stealer, RedLine, Lumma
- Backdoored legitimate installers (real software + embedded malware)

### Notepad++ Supply Chain Compromise (2025-2026)

A particularly sophisticated attack attributed to Chinese state-sponsored actors:

1. Attackers compromised the shared hosting provider for Notepad++ update infrastructure (June 2025)
2. Gained control of the WinGUp update distribution system
3. Intercepted update requests and fingerprinted users by IP range and geolocation
4. Selectively redirected targeted users to trojanized Notepad++ installers (versions 8.8.2 through 8.8.9)
5. Non-targeted users received legitimate updates -- making detection extremely difficult

**Key lesson:** Even official update mechanisms served from legitimate infrastructure can be compromised at the hosting/CDN layer. Targeted delivery by IP fingerprinting evades broad detection.

### Chinese-Language SEO Campaigns (2025)

HiddenGh0st, Winos, and kkRAT malware distributed via:
- Fake software sites targeting Chinese-speaking users
- SEO plugins injected into compromised legitimate sites
- Lookalike domains mimicking popular Chinese software portals

---

## 4. Gaming & Modding Community Attacks

Gaming communities are high-value targets because: (a) younger demographics with less security awareness, (b) mods/plugins routinely require elevated permissions, (c) modding platforms have minimal security review, (d) gaming credentials and in-game items have monetary value.

### Fractureiser -- Minecraft (June 2023)

**The most significant gaming supply chain attack to date.**

**Attack chain:**
1. Attackers compromised CurseForge and BukkitDev maintainer accounts
2. Injected malicious code into copies of popular Minecraft mods and plugins
3. Infected mods distributed through CurseForge -- including popular modpacks like "Better Minecraft"
4. Malicious JARs as early as mid-April 2023; discovered June 2023
5. Luna Pixel Studios developer tried an infected mod, leading to supply chain cascade into their modpacks

**Malware capabilities:**
- **Self-replication**: Infected every `.jar` file on the filesystem by injecting Stage 0 loader
- **Credential theft**: Stole browser cookies, saved passwords, payment information
- **Token theft**: Stole Discord tokens, Minecraft session tokens
- **Clipboard hijacking**: Replaced cryptocurrency wallet addresses
- **Multi-stage**: Downloaded additional payloads from C2 servers
- **Cross-platform**: Targeted both Windows and Linux

**Key lesson:** Modding platforms lack the security infrastructure of major package registries. A single compromised account on CurseForge had blast radius comparable to a major npm incident. The self-replicating nature meant sharing any `.jar` from an infected system spread the infection.

**Community response:**
- Fractureiser Mitigation Team formed (June 8, 2023 meeting)
- CurseForge implemented additional account security measures
- Community-developed detection tools released
- Discussion of mod signing and verification standards

### Steam Workshop Attacks

- **People Playground** (Feb 2026): Malware spread through Steam Workshop mods, deleting other mods and save files
- **Slay the Spire / Downfall mod** (Dec 2023): Developer's Steam and Discord accounts hijacked; malicious update pushed that could overtake the game completely
- **Cities Skylines 2** (2024): DLL hijacking attack via Workshop mod, confirmed by Paradox Interactive

**Structural problem:** Steam Workshop mods are *not* scanned or manually vetted by Valve. Games with Lua/DLL mod support effectively allow arbitrary code execution. Users treat Workshop content as implicitly trusted because it's on Steam's platform.

### Roblox Developer Targeting

- Year-long npm malware campaign impersonating the popular "noblox.js" library (Roblox API wrapper)
- Dozens of typosquat packages published to steal credentials and deploy RATs
- Malware capabilities: Discord token theft, system info harvesting, persistence, Quasar RAT deployment
- Separate campaigns use fake "FPS Booster" YouTube videos linking to Discord servers distributing infostealers

### Discord as Attack Infrastructure

Discord is both a target and a tool:

**As a target:**
- Fake Safeguard bots prompt users to "verify" via phishing sites mimicking Discord UI
- Token stealers specifically target Discord credentials for account takeover
- Compromised Discord bots used to distribute malware links in trusted servers

**As C2 infrastructure:**
- Malware uses Discord bot APIs for command and control
- Stolen data exfiltrated to private Discord channels
- Discord webhook URLs used as dead-simple data exfiltration endpoints
- CDN (`cdn.discordapp.com`) used to host malware payloads

### Top Sources of Gaming-Related Infections (2025 study)

1. Grand Theft Auto (unofficial mods/cheats)
2. Roblox
3. Valorant
4. Counter-Strike
5. Fortnite

---

## 5. Browser Extension Attacks

### Attack Vectors

1. **Developer account phishing**: Targeted phishing emails claiming Chrome Web Store policy violations, threatening extension removal
2. **OAuth token theft**: Phishing pages grant attacker OAuth permissions to publish updates
3. **Extension purchase**: Buying legitimate extensions from original developers, then pushing malicious updates
4. **Malicious new extensions**: Publishing extensions with hidden malicious functionality
5. **Dependency attacks**: Injecting malicious code into shared libraries used by extensions

### Major Incidents

#### Cyberhaven / December 2024 Campaign

- Threat actor phished developer accounts via emails impersonating Chrome Web Store
- Pushed malicious updates to **35 extensions** affecting **3.7 million users**
- Cyberhaven's extension specifically compromised on Dec 26, 2024
- Malicious code harvested OAuth tokens from Google Workspace, Slack, and Jira
- Exfiltrated HTTP headers and DOM content based on dynamic configuration from C2

#### TamperedChef Campaign (February 2025)

- GitLab Threat Intelligence uncovered compromise of **16 Chrome extensions**
- **3.2 million users** affected
- Attack methods: purchasing extensions from developers OR compromising developer accounts
- Injected JavaScript connected to remote C2 for dynamic command execution
- Could receive and execute arbitrary commands

#### Firefox Cryptocurrency Extension Attacks

- 45 malicious Firefox extensions impersonating legitimate crypto wallets
- Mimicked: Coinbase, MetaMask, Trust Wallet, Phantom, Exodus, OKX, Keplr, MyMonero, Bitget, Leap
- Designed to steal private keys, seed phrases, and redirect transactions

### Malicious Extension Behaviors

- **Credential harvesting**: Intercepting login forms and exfiltrating credentials
- **Session hijacking**: Stealing cookies and OAuth tokens
- **Browser hijacking**: Redirecting URLs through affiliate/malware links
- **Traffic interception**: Man-in-the-browser for financial transactions
- **Cryptojacking**: Using browser compute for cryptocurrency mining
- **Surveillance**: Capturing browsing history, keystrokes, screenshots

### Scale

- A 2025 study (arxiv.org) provides systematic analysis of malicious browser extension trends
- 1.7 million+ users installed malicious extensions in a single campaign cluster
- Total affected users across 2024-2025 campaigns: millions
- Extensions with legitimate functionality + hidden malicious code are hardest to detect

---

## 6. Open Source Maintainer Compromise

### The XZ Utils Backdoor (CVE-2024-3094) -- The Gold Standard of Social Engineering

**Timeline:**
- **November 2021**: Account "Jia Tan" (JiaT75) begins contributing to xz-utils
- **2022**: Sock puppet accounts (Jigar Kumar, krygorin4545, misoeater91) pressure the sole maintainer Lasse Collin, complaining about slow releases and suggesting new maintainers
- **2022-2023**: Jia Tan builds trust through legitimate contributions, gradually gains co-maintainer status
- **February 2024**: Jia Tan pushes xz-utils versions 5.6.0 and 5.6.1 containing a backdoor
- **March 29, 2024**: Andres Freund discovers the backdoor via SSH performance anomalies

**Technical details:**
- Backdoor gave anyone with a specific **Ed448 private key** remote code execution via OpenSSH
- CVSS score: **10.0** (maximum)
- Backdoor was hidden in binary test files, activated through the build system (not visible in source review)
- Targeted `liblzma`, which is linked by `sshd` on many Linux distributions via systemd
- Only affected specific build configurations -- indicating deep knowledge of Linux distribution packaging

**Why it nearly succeeded:**
- 2+ years of patient social engineering
- Legitimate, helpful contributions built trust
- Exploited maintainer burnout in a critical but underfunded project
- Sock puppets created artificial community pressure for the takeover
- Backdoor hidden in test data, not in reviewable source code
- Caught by accident (performance regression), not by security review

**Community response:**
- OpenSSF and OpenJS Foundation issued joint warning that this "may not be an isolated incident"
- Reported similar social engineering attempts against JavaScript projects hosted by OpenJS
- Warning signs identified: "friendly yet aggressive and persistent pursuit" by unknown community members seeking maintainer status

### GhostAction / GitHub Actions Compromise (September 2025)

- GitGuardian discovered campaign affecting **327 GitHub users** across **817 repositories**
- Attackers injected malicious GitHub Actions workflows
- Exfiltrated **3,325 secrets** (API keys, tokens, credentials)
- Exploited the trust model of GitHub Actions where workflows have access to repository secrets

### Patterns of Maintainer Social Engineering

1. **Long-game trust building**: Months to years of legitimate contributions before injecting malicious code
2. **Burnout exploitation**: Targeting overworked solo maintainers of critical infrastructure
3. **Sock puppet pressure**: Creating fake community members who demand changes or new maintainers
4. **Ownership transfer requests**: Approaching maintainers of abandoned or low-activity packages
5. **Expired domain hijacking**: Re-registering expired maintainer email domains to reset passwords (ctx/phpass incident)
6. **Corporate employee targeting**: Phishing developers at companies who maintain popular packages

---

## 7. Defensive Measures by Vector

### 7.1 Package Registry Defenses

**Package Signing & Verification:**
- npm: Package provenance via Sigstore (npm provenance) -- links packages to source repos and build systems
- PyPI: Trusted Publishers (OIDC-based, eliminates long-lived API tokens)
- NuGet: Package signing certificates, but dependency confusion still possible without `packageSourceMapping`
- Maven: Strict group ID verification via DNS ownership

**Lockfiles & Pinning:**
- Always commit lockfiles (`package-lock.json`, `Pipfile.lock`, `poetry.lock`)
- Pin exact versions, not ranges
- Use `npm ci` (not `npm install`) in CI/CD
- NuGet: Configure `packageSourceMapping` in `nuget.config` to bind package names to specific sources

**Scanning & Monitoring:**
- Socket.dev: Real-time detection of suspicious package behavior (install scripts, network access, obfuscation)
- Snyk: Vulnerability and malicious package scanning
- Checkmarx Supply Chain Security: Behavioral analysis of packages
- `npm audit`, `pip-audit`, `dotnet list package --vulnerable`
- OpenSSF Scorecard: Automated security health assessment of open source projects

**Policy:**
- Review all new dependencies before adding them
- Audit `postinstall` / `preinstall` scripts (npm: `--ignore-scripts` then selectively allow)
- Prefer packages with provenance attestations
- Monitor for dependency updates that add new capabilities (network, filesystem, child_process)

### 7.2 Build Pipeline Defenses

**SLSA Framework (Supply-chain Levels for Software Artifacts):**

| Level | Requirements | Protects Against |
|-------|-------------|------------------|
| SLSA 1 | Automated provenance generation describing how artifact was built | Basic provenance |
| SLSA 2 | Digitally signed provenance from build platform | Provenance forgery |
| SLSA 3 | Hermetic builds, ephemeral environments, cryptographically signed provenance | Build environment tampering |
| SLSA 4 | Two-party review of all source changes | Single compromised insider |

**Sigstore / Cosign:**
- **Fulcio**: Issues short-lived certificates tied to OIDC identity (no long-lived keys to steal)
- **Cosign**: Signs and verifies container images, binaries, and artifacts
- **Rekor**: Append-only transparency log recording all signatures (tamper-evident)
- Eliminates the "stolen signing key" problem by making keys ephemeral

**Reproducible Builds:**
- Allows independent verification that a binary was built from claimed source
- Debian, Arch Linux, and others have reproducible build initiatives
- Catches SolarWinds-style attacks where the build output differs from what the source code would produce
- Tools: `diffoscope`, `reprotest`, `in-toto`

**CI/CD Hardening:**
- Never fetch scripts from remote URLs at build time (Codecov lesson)
- Pin all CI/CD action versions by SHA, not tag
- Use ephemeral build environments (no persistent state between builds)
- Limit CI secret access to minimum necessary
- Enable branch protection with required reviews
- Audit GitHub Actions for third-party actions with excessive permissions

### 7.3 Software Update Defenses

**For software vendors:**
- Implement The Update Framework (TUF) for secure update delivery
- Sign updates with keys stored in HSMs, not build servers
- Implement binary transparency logs
- Use reproducible builds to allow third-party verification
- Separate build signing from distribution infrastructure

**For consumers:**
- Verify update signatures independently where possible
- Monitor for unexpected update behavior
- Use EDR/XDR that monitors signed software for anomalous post-update behavior
- For critical infrastructure: delay updates and test in isolated environments
- Subscribe to vendor security advisories

### 7.4 Fake Download Site Defenses

**For users:**
- Always navigate to official sites directly (bookmark them), never via search results
- Verify download hashes against those published on official sites
- Be suspicious of Google Ads results for software downloads
- Use official package managers (winget, brew, apt, choco) instead of downloading installers
- Check certificate details on download sites

**For organizations:**
- DNS filtering to block known malicious domains
- Application allowlisting -- only approved software can execute
- EDR with behavioral analysis (catches trojanized installers)
- Web content filtering blocking ad-served downloads
- User training specifically about fake download sites

### 7.5 Gaming/Modding Community Defenses

- Only install mods from official platforms (CurseForge, Steam Workshop, Modrinth)
- Even on official platforms, check mod age, download count, author history
- Run modded games in sandboxed environments where possible
- Use antivirus that scans JAR/DLL files
- Be skeptical of Discord-distributed mods, "FPS boosters," or free premium content
- For Minecraft: Use Prism Launcher or similar launchers with mod verification
- Post-fractureiser: Community-developed detection tools available on GitHub

### 7.6 Browser Extension Defenses

**For users:**
- Minimize installed extensions (each is an attack surface)
- Review permissions requested by extensions before installing
- Prefer extensions from well-known, audited developers
- Regularly audit installed extensions and remove unused ones
- Disable automatic extension updates; review changelogs before updating
- Never install extensions from outside official stores

**For organizations:**
- Use Chrome Enterprise policies to allowlist/blocklist extensions
- Browser extension risk assessment tools (Spin.AI, CRXcavator)
- Monitor for new extension installations across fleet
- Block extension installation from non-approved sources
- Regular audits of approved extensions for ownership changes

**Chrome Web Store defenses:**
- Manifest V3 reduces extension capabilities (more limited APIs, declarativeNetRequest)
- Google's automated malware scanning
- Developer verification requirements
- Publication delays for review (but phishing bypasses this by updating existing extensions)

### 7.7 Maintainer Compromise Defenses

**For maintainers:**
- Enable MFA on all registry and source control accounts
- Use hardware security keys (YubiKey) -- phishing-resistant
- Be wary of social engineering patterns: pressure to add co-maintainers, sock puppet complaints
- OpenSSF warning signs: "friendly yet aggressive and persistent pursuit" of maintainer access
- Require GPG-signed commits
- Never transfer ownership to accounts without established identity

**For consumers of open source:**
- Monitor projects for maintainer changes (especially sole-maintainer projects)
- OpenSSF Scorecard checks for security practices
- Use tools that detect behavioral changes in package updates
- For critical dependencies: fork and maintain internally, cherry-pick upstream changes after review
- SBOM + vulnerability monitoring for transitive dependencies

### 7.8 SBOM (Software Bill of Materials)

**CISA 2025 Minimum Elements:**
- Updated from 2021 NTIA guidance with expanded requirements
- Covers: component identification, dependency relationships, licensing, known vulnerabilities
- Formats: SPDX 3, CycloneDX
- Tools: Syft (generation), Grype (vulnerability matching), GUAC (graph analysis)

**Operational use:**
- Inventory all software components including transitive dependencies
- Automate SBOM generation in CI/CD pipelines
- Cross-reference SBOMs against vulnerability databases continuously
- SBOM sharing between vendors and customers for supply chain transparency
- Required for US federal government software procurement (Executive Order 14028)

---

## 8. Key Metrics & Trends

### Attack Volume

| Metric | Value | Source |
|--------|-------|--------|
| Malicious packages published (annual) | 454,648 | Sonatype 2025 |
| YoY increase in malicious packages | 156% | Sonatype 2025 |
| Breaches from supply chain attacks | 15% | Industry aggregate |
| npm malicious package reports (2018 vs 2024) | 38 vs 2,168 | Snyk |
| Browser extension users affected (Dec 2024) | 3.7 million | Cyberhaven incident |
| XZ Utils CVSS score | 10.0 | NVD |

### Trend Analysis (2023-2026)

1. **Cross-ecosystem attacks increasing**: Campaigns now target npm + PyPI + Maven simultaneously (MUT-8694, Shai-Hulud v2)
2. **Chained supply chain attacks**: 3CX was compromised via a prior compromise of Trading Technologies
3. **Nation-state participation**: XZ Utils (suspected state actor), Notepad++ (Chinese APT), 3CX (Lazarus/DPRK), SolarWinds (Russian SVR)
4. **Targeting of security tools**: Attackers increasingly target the tools organizations use to defend themselves (Codecov, CI/CD pipelines)
5. **AI-assisted attacks**: Emerging use of AI to generate convincing typosquat packages and social engineering content at scale
6. **Gaming as entry vector**: Gaming malware on personal devices leading to corporate credential theft (Roblox-to-corporate pipeline)
7. **Update mechanism targeting**: Shift from compromising source code to compromising distribution infrastructure (hosting providers, CDNs, update servers)

### Defensive Maturity

The industry is responding but lags behind attack sophistication:
- SLSA, Sigstore, and SBOM adoption accelerating but not yet universal
- npm provenance and PyPI Trusted Publishers are significant improvements
- Chrome Manifest V3 reduces but does not eliminate extension attack surface
- No equivalent security framework exists for gaming mod ecosystems
- XZ Utils demonstrated that even years of trust-building can be a social engineering attack -- technical controls alone are insufficient

---

## Sources

### Package Attacks
- [Rescana: In-Depth Analysis of npm Supply Chain Poisoning](https://www.rescana.com/post/in-depth-analysis-supply-chain-poisoning-of-popular-npm-packages-exploiting-event-stream-ua-parser)
- [ArmorCode: Inside the September 2025 NPM Supply Chain Attack](https://www.armorcode.com/blog/inside-the-september-2025-npm-supply-chain-attack)
- [Datadog: MUT-8694 npm and PyPI Malicious Campaign](https://securitylabs.datadoghq.com/articles/mut-8964-an-npm-and-pypi-malicious-campaign-targeting-windows-users/)
- [Trail of Bits: Supply Chain Attacks Are Exploiting Our Assumptions](https://blog.trailofbits.com/2025/09/24/supply-chain-attacks-are-exploiting-our-assumptions/)
- [GitGuardian: Typosquatting and Dependency Confusion](https://blog.gitguardian.com/protecting-your-software-supply-chain-understanding-typosquatting-and-dependency-confusion-attacks/)
- [Checkmarx: Chalk and 17 Other NPM Packages Compromised](https://checkmarx.com/zero-post/chalk-and-17-other-npm-packages-compromised-in-supply-chain-attack/)
- [Hacker News: Shai-Hulud v2 Spreads From npm to Maven](https://thehackernews.com/2025/11/shai-hulud-v2-campaign-spreads-from-npm.html)
- [Hacker News: Hidden Logic Bombs in NuGet Packages](https://thehackernews.com/2025/11/hidden-logic-bombs-in-malware-laced.html)
- [CISA: Widespread Supply Chain Compromise Impacting npm Ecosystem](https://www.cisa.gov/news-events/alerts/2025/09/23/widespread-supply-chain-compromise-impacting-npm-ecosystem)
- [Sonatype: History of Software Supply Chain Attacks](https://www.sonatype.com/resources/vulnerability-timeline)

### Build Pipeline Compromises
- [Beyond Identity: SolarWinds, Kaseya, and NotPetya Methods](https://www.beyondidentity.com/resource/software-supply-chain-attack-methods-behind-solarwinds-kaseya-and-notpetya-and-how-to-prevent-them)
- [Sonatype: 3CX Supply Chain Attack Analysis](https://www.sonatype.com/blog/another-solarwinds-the-latest-software-supply-chain-attack-on-3cx)
- [Malwarebytes: Codecov Supply Chain Compromise](https://www.malwarebytes.com/blog/awareness/2021/04/codecov-supply-chain-compromise-likened-to-solarwinds-attack)
- [Computer Weekly: Codecov Supply Chain Attack](https://www.computerweekly.com/news/252499587/Codecov-supply-chain-attack-has-echoes-of-SolarWinds)

### Fake Software Distribution
- [ThreatLocker: Notepad++ Supply Chain Compromise](https://www.threatlocker.com/blog/notepad-supply-chain-compromise-trojanized-updates-used-in-suspected-nation-state-attack)
- [Hacker News: Notepad++ Update Mechanism Hijacked](https://thehackernews.com/2026/02/notepad-official-update-mechanism.html)
- [BleepingComputer: Malware via Google Search Ads for VLC, 7-Zip, CCleaner](https://www.bleepingcomputer.com/news/security/hackers-push-malware-via-google-search-ads-for-vlc-7-zip-ccleaner/)
- [Vectra: SEO Poisoning Attacks](https://www.vectra.ai/topics/seo-poisoning)
- [Hacker News: HiddenGh0st, Winos and kkRAT SEO Campaigns](https://thehackernews.com/2025/09/hiddengh0st-winos-and-kkrat-exploit-seo.html)

### Gaming & Modding
- [GitHub: Fractureiser Information Repository](https://github.com/trigram-mrp/fractureiser)
- [BleepingComputer: Fractureiser Malware via CurseForge](https://www.bleepingcomputer.com/news/security/new-fractureiser-malware-used-curseforge-minecraft-mods-to-infect-windows-linux/)
- [Kaspersky: Fractureiser Attacks Minecraft Players](https://usa.kaspersky.com/blog/curseforge-compromised-fractureiser/28472/)
- [GamingOnLinux: People Playground Steam Workshop Malware](https://www.gamingonlinux.com/2026/02/steam-game-people-playground-hit-by-malware-via-the-steam-workshop/)
- [Hackread: Malware Exploits NPM to Attack Roblox Developers](https://hackread.com/malware-exploits-npm-attack-roblox-developers/)

### Browser Extensions
- [arxiv: Study on Malicious Browser Extensions in 2025](https://arxiv.org/html/2503.04292v2)
- [GitLab: Malicious Browser Extensions Impacting 3.2M Users](https://gitlab-com.gitlab.io/gl-security/security-tech-notes/threat-intelligence-tech-notes/malicious-browser-extensions-feb-2025/)
- [Pulsedive: Compromised Browser Extensions Jan 2025](https://blog.pulsedive.com/compromised-browser-extensions-a-growing-threat-vector/)
- [Malwarebytes: Millions Spied on by Malicious Extensions](https://www.malwarebytes.com/blog/news/2025/07/millions-of-people-spied-on-by-malicious-browser-extensions-in-chrome-and-edge)

### Maintainer Compromise
- [Black Duck: XZ Utils Backdoor Analysis](https://www.blackduck.com/blog/xz-utils-backdoor-supply-chain-attack.html)
- [Wikipedia: XZ Utils Backdoor](https://en.wikipedia.org/wiki/XZ_Utils_backdoor)
- [OpenSSF: XZ Backdoor CVE-2024-3094](https://openssf.org/blog/2024/03/30/xz-backdoor-cve-2024-3094/)
- [Checkmarx: Most Advanced Supply Chain Attack Known to Date](https://checkmarx.com/blog/backdoor-discovered-in-xz-the-most-advanced-supply-chain-attack-known-to-date/)
- [Akamai: XZ Utils Backdoor Analysis](https://www.akamai.com/blog/security-research/critical-linux-backdoor-xz-utils-discovered-what-to-know)
- [CSO Online: Years-Long Supply Chain Compromise Effort](https://www.csoonline.com/article/2077692/dangerous-xz-utils-backdoor-was-the-result-of-years-long-supply-chain-compromise-effort.html)

### Defenses & Frameworks
- [CISA: Software Bill of Materials (SBOM)](https://www.cisa.gov/sbom)
- [CISA: 2025 Minimum Elements for SBOM](https://www.cisa.gov/resources-tools/resources/2025-minimum-elements-software-bill-materials-sbom)
- [SLSA: Supply-chain Levels for Software Artifacts](https://slsa.dev/)
- [Faith Forge Labs: Software Supply Chain Security in 2025](https://faithforgelabs.com/blog_supplychain_security_2025.php)
- [OpenSSF: SBOMs in the Era of the CRA](https://openssf.org/blog/2025/10/22/sboms-in-the-era-of-the-cra-toward-a-unified-and-actionable-framework/)