FBI NCIC breach: the national crime database was reportedly hacked. What we know, what we don't, and the FBI's second breach in two months
SockAnalyst · Security+ certified analyst.
What happened
On Friday, November 20, 2026, CNN reported that the FBI is investigating an apparent breach of the National Crime Information Center (NCIC), citing two people briefed on the investigation. NBC News and the Associated Press reported the same, three sources told Fox News that hackers breached NCIC, and a law enforcement source confirmed the hack to ABC News. CONFIRMED: the FBI is investigating an intrusion into NCIC, and President Trump acknowledged it in a Fox News interview on Saturday, November 21 ("we just heard about it, and I will say that it's not good. I don't like that"). REPORTED, NOT CONFIRMED BY THE FBI: the intrusion was found in recent days (CNN, via BleepingComputer); the FBI is still working to determine the entry point (Fox News sources); two people told MS NOW the hackers accessed NCIC, but it is unclear what data was extracted (via CNBC). UNKNOWN as of Sunday morning, November 22: who did it (no group has claimed it, and BleepingComputer reports no indication it is tied to ShinyHunters or the September breach), how the attackers got in (no CVE or vector has been reported), when it started, whether records were read, stolen or altered, and whether NCIC availability was affected. The FBI has not issued a public statement and declined to comment or did not respond to AP, ABC, NBC, CNN, Fox, CNBC, Reuters, BBC, Axios and BleepingComputer. No CISA advisory about NCIC has been published. Why it matters: police check NCIC for warrants, wanted and missing persons, criminal histories, stolen vehicles and guns, protection orders and background checks, including during traffic stops. A former FBI official told CNN the bigger worry is "whether they could compromise the accuracy of the information that officers rely on." Axios notes a breach doesn't necessarily mean the whole database was taken. Context, the FBI's earlier incidents: in September 2026, ShinyHunters claimed the FBIJobs.gov breach, and the FBI said on October 6 it was "the result of a security failure of a platform managed by a third-party organization — after a contractor failed to implement a security patch explicitly issued to secure the platform" (arrests followed); in February 2023 the FBI contained an incident on a New York Field Office network; in November 2021 a LEEP portal misconfiguration was abused to send fake emails from an FBI address. Nothing links any of those incidents to NCIC. This page will be updated in place as facts are confirmed.
Who's affected
Potentially anyone with an NCIC record (people who were arrested, are wanted, were reported missing, or are named in protection orders, plus stolen-property records) and the federal, state, local and tribal agencies that rely on NCIC. Scope is not confirmed: no source has said which records, if any, were taken or changed. Expect scammers to exploit the headlines with "your criminal record was exposed" or "NCIC verification" phishing and pretext calls aimed at the public, agency staff, dispatchers and help desks.
✅ Fix / patch
- No fix has been published, because no vector or CVE has been reported. These are general defensive steps, not a remediation for this incident.
- Agencies with NCIC/CJIS access: watch for notices from the FBI CJIS Division and your state CJIS Systems Agency, and follow their instructions rather than social media or press reports.
- Brief help desks, dispatch and records staff to expect NCIC-, CJIS- and FBI-themed phishing and pretext calls. Verify any request to 'confirm' credentials, records or system access through a known phone number.
- Keep confirming NCIC hits with the agency that entered the record before acting; NCIC hits alone don't give probable cause (Axios, citing the FBI's 2022 overview). That habit also protects you if record integrity is ever in question.
- Apply the lesson the FBI confirmed from September: inventory third-party-hosted and contractor-managed systems, write KEV patching deadlines into contracts, and verify them. If you run Oracle PeopleSoft, confirm you're patched for the PeopleSoft flaw CISA added to KEV on June 12, 2026 (see the CISA context source below). No source links that flaw to the NCIC incident.
🔎 Quick hunt check
No IOCs, vector or threat actor have been published for the NCIC intrusion, so there is nothing to hunt for this attacker. These queries check headline-driven exposure only: (1) inbound email that mentions NCIC, CJIS, the FBI or 'criminal record' together with breach, verify, exposed or password wording and does not come from a .gov domain; (2) users who clicked links in such messages.
IOCs
No IOCs (IPs, domains or hashes) published by the sources yet.
No public IOCs. The FBI has published no statement, indicators or vector for the NCIC intrusion. T1566 and T1598 reflect the expected headline-driven phishing risk covered by the queries, not observed attacker activity.
Hunt queries
Starting points built only from published indicators. Field names vary; tune before use.
```FBI NCIC breach headlines: NCIC/CJIS/FBI-themed lure emails from non-.gov senders (exposure check, not attacker IOCs)```
index=* earliest=11/20/2026:00:00:00 (sourcetype=*mail* OR sourcetype=*o365* OR tag=email)
| eval sender=lower(coalesce(src_user, sender, from, SenderAddress, "")), subj=coalesce(subject, Subject, "")
| eval sender_domain=replace(sender, "^.*@", "")
| where match(subj, "(?i)\b(NCIC|CJIS|FBI|criminal (record|history))\b") AND match(subj, "(?i)(breach|hack|exposed|leak|verify|verification|confirm|password|account|record)")
| where NOT match(sender_domain, "(\.|^)gov$")
| stats count min(_time) as first_seen max(_time) as last_seen values(subj) as subjects values(recipient) as recipients by sender, sender_domain
| convert ctime(first_seen) ctime(last_seen)
| sort - count// FBI NCIC breach headlines: NCIC/CJIS/FBI-themed lure emails from non-.gov senders + clicks (exposure check, not attacker IOCs)
let Since = datetime(2026-11-20);
let Lures = EmailEvents
| where TimeGenerated >= Since and EmailDirection == "Inbound"
| where Subject matches regex @"(?i)\b(NCIC|CJIS|FBI|criminal (record|history))\b"
| where Subject matches regex @"(?i)(breach|hack|exposed|leak|verify|verification|confirm|password|account|record)"
| where not(SenderFromDomain endswith ".gov");
Lures
| join kind=leftouter (UrlClickEvents | where TimeGenerated >= Since | project NetworkMessageId, ClickedUrl = Url, ClickTime = TimeGenerated, ClickedBy = AccountUpn) on NetworkMessageId
| summarize Messages = dcount(NetworkMessageId), Recipients = make_set(RecipientEmailAddress, 50), Clicks = countif(isnotempty(ClickedUrl)), ClickedBy = make_set(ClickedBy, 50), Subjects = make_set(Subject, 20) by SenderFromAddress, SenderFromDomain
| order by Clicks desc, Messages desc⏱ CISA deadline
Not in CISA KEV as of Nov 22, 2026.
Sources
- AP: FBI investigating apparent hack of its key national criminal justice database (Nov 21, 2026)
- NBC News: FBI investigating potential breach of its crime database (Nov 20, 2026)
- CNN via WPTZ: Trump downplays breach of FBI's crime database (Nov 21, 2026)
- ABC News: FBI's national crime database targeted in hack, Trump says (Nov 21, 2026)
- Fox News: FBI probes second cyberattack in months as hackers breach key crime database, sources say (Nov 21, 2026)
- CNBC: Trump says there could be a 'positive spin' from the latest FBI database hack (Nov 21, 2026; cites MS NOW sources)
- BleepingComputer: FBI reportedly hacked again, this time targeting nationwide police database (Nov 21, 2026)
- Axios: Latest hack of FBI puts personal records at risk (Nov 21, 2026)
- Reuters via CNBC: FBI's criminal information database hacked, CNN reports (Nov 21, 2026)
- BBC: FBI reportedly investigating apparent hack of its criminal database (Nov 21, 2026)
- Prior: NBC News, FBI says contractor failure led to hack of its jobs website (Oct 6, 2026)
- Prior: SecurityWeek, FBI blames contractor's missed patch for ShinyHunters breach (Oct 6, 2026)
- Prior: BleepingComputer, ShinyHunters claims FBI hack in PeopleSoft breach (Sep 22, 2026)
- Prior: FBI statement on incident involving fake emails (Nov 2021)
- Prior: Reuters, FBI says it has contained cyber incident on bureau's network (Feb 2023)
- Context: CISA adds CVE-2026-35273 (Oracle PeopleSoft) to KEV (Jun 12, 2026; not linked to NCIC)
Primary source note: The FBI has not published a statement, notice or advisory on the NCIC intrusion. Facts come from news reports citing unnamed sources and from President Trump's on-record Fox News interview.
Related playbooks
- NTT Docomo: up to ~300k customer records leaked from My docomo / Online Shop · Breach · 2026-11-06
- Microsoft Entra Connect Health API flaw exploited: admin email addresses and tenant metadata exposed, Microsoft notifying affected tenants · Breach · 2026-11-22
- Bell Canada breach: 'agentic' threat actor stole enterprise customer data from a circuit-provisioning Maximo pre-production system · Breach · 2026-11-21
Get the SockAnalyst Weekly Brief free, every Thursday.
One email a week with the KEV deadlines, patches and hunt queries that matter. New playbooks still post here on the site every morning.
Subscribe free
SockAnalyst