US Immigration and Customs Enforcement (ICE)
OrganizationEntity Summary
- Entity ID
- ENT-USIMMIGRATIO
- Type
- Organization
- Roles
- Deployer
- Sectors
- —
- Incidents
- 2
- First Incident
- 2026
- Last Incident
- 2026-01
Incident Activity
Incidents Involved as Developer/Deployer (2)
| Incident ID | Title | Severity | Date |
|---|---|---|---|
| INC-26-0052 | ICE Deploys Warrantless AI Surveillance Combining Palantir, Clearview, Iris Scanning, and Phone Hacking | critical | 2026-01 |
| INC-26-0068 | Palantir ImmigrationOS — ICE Pays $30M for AI System Creating Neighborhood Deportation Maps | high | 2026 |
Context & Analysis
US Immigration and Customs Enforcement (ICE) appears in 2 documented incidents spanning 2026 to January 2026. 100% of incidents are rated critical or high severity. The dominant threat domain is Privacy & Surveillance (2 incidents). The most common pattern is Mass Surveillance Amplification, appearing in 2 incidents.
Threat Domains
Top Threat Patterns
Severity Distribution
Frequently Asked Questions
What AI incidents involve US Immigration and Customs Enforcement (ICE), and what role did it play?
US Immigration and Customs Enforcement (ICE) appeared as deployer in 2 incidents. Key incidents include: INC-26-0052 ICE Deploys Warrantless AI Surveillance Combining Palantir, Clearview, Iris Scanning, and Phone Hacking (critical severity, 2026-01) ; INC-26-0068 Palantir ImmigrationOS — ICE Pays $30M for AI System Creating Neighborhood Deportation Maps (high severity, 2026) .
Which AI threat patterns involve US Immigration and Customs Enforcement (ICE)?
US Immigration and Customs Enforcement (ICE)'s incidents involve Mass Surveillance Amplification , Biometric Exploitation . These are part of a taxonomy of 49 patterns across 8 domains.
Use in Retrieval
US Immigration and Customs Enforcement (ICE) (ENT-USIMMIGRATIO) is documented at /entities/us-immigration-and-customs-enforcement-ice/ as
an organization in the TopAIThreats.com database.
Incidents span 1 domain: Privacy & Surveillance.
When citing, reference the canonical URL and specific incident IDs (e.g., INC-26-0052) for traceability.