# Supply Chain Attacks


📂 ai-red-teaming

## AI RED TEAMING TECHNIQUES

# Supply Chain Attacks

Testing AI model and data supply chain security vulnerabilities

## Available Techniques

### AI Model Poisoning

Injection of malicious data into AI training datasets to corrupt model behavior, causing models to learn incorrect patterns or exhibit harmful behaviors.

#### KEY FEATURES

- •
Training data manipulation

- •
Gradual behavior modification

- •
Trigger-based activation

#### PRIMARY DEFENSES

- •
Data validation and sanitization

- •
Source verification and digital signatures

- •
Statistical anomaly detection

#### KEY RISKS

### Malicious Model Distribution

Distribution of compromised AI models through legitimate channels like model repositories, containing hidden malicious functionality or backdoors.

#### KEY FEATURES

- •
Repository infiltration

- •
Typosquatting attacks

- •
Version poisoning

#### PRIMARY DEFENSES

- •
Model signature verification

- •
Automated security scanning

- •
Reputation-based filtering

#### KEY RISKS

### AI Dependency Confusion

Exploitation of package management systems to inject malicious AI libraries or dependencies into AI development workflows.

#### KEY FEATURES

- •
Package name similarity

- •
Version number manipulation

- •
Automated installation triggers

#### PRIMARY DEFENSES

- •
Package pinning and lock files

- •
Private package repositories

- •
Dependency scanning tools

#### KEY RISKS

### AI Library Vulnerability Exploitation

Exploitation of security vulnerabilities in popular AI/ML libraries and frameworks that are widely used in the AI development ecosystem.

#### KEY FEATURES

- •
Known CVE exploitation

- •
Zero-day vulnerability discovery

- •
Framework-specific attacks

#### PRIMARY DEFENSES

- •
Regular security updates

- •
Vulnerability scanning automation

- •
Runtime protection mechanisms

#### KEY RISKS

### Ethical Guidelines for Supply Chain Attacks

When working with supply chain attacks techniques, always follow these ethical guidelines:

- • Only test on systems you own or have explicit written permission to test

- • Focus on building better defenses, not conducting attacks

- • Follow responsible disclosure practices for any vulnerabilities found

- • Document and report findings to improve security for everyone

- • Consider the potential impact on users and society

- • Ensure compliance with all applicable laws and regulations

FROM THE ENGINEER BEHIND THIS CATALOG

## Get your agent system red-teamed

The attacks documented here work on production agent systems every day. Have yours tested before someone else does: prompt injection, jailbreaks, tool misuse and data exfiltration, with every finding written up next to its fix.

€750 instead of €1,500, one week, written report and walkthrough call, until 30 September

## AI Red Teaming

## AI Red Teaming Techniques