The FBI's NCIC Crime Database Was Reportedly Breached. Anonymous Sources Say So, the FBI Hasn't, and No One Has Claimed It. What Police IT and the Public Should Check Now

If you run IT or CJIS security for a police department or sheriff's office, do three things this weekend: ask your state CJIS Systems Agency for your agency's recent NCIC transaction log and look for queries nobody on shift made, confirm every account that can reach criminal justice information is behind multi-factor authentication with departed staff removed, and warn your people and the companies you send records requests to that fake "emergency data requests" in your agency's name are the most likely thing to follow. If you are a member of the public, nothing has been asked of you yet, and nobody legitimate will call you demanding payment to clear a warrant.
Here is why. On Friday, November 20, CNN reported that the FBI is investigating an apparent breach of the National Crime Information Center, NCIC, the database police across the country query during traffic stops, investigations and background checks. The Associated Press and Fox News followed on Saturday with their own anonymous sources. The FBI has not confirmed it.
What is reported, and by whom
Read the sourcing carefully, because it is all there is:
- CNN, which broke the story, cited "two people briefed on the investigation." CNN's page returned an HTTP 451 to our reader, so we worked from the outlets that summarize it, listed in Sources.
- The Associated Press (Eric Tucker) says it confirmed the report with "a person familiar with the matter" who "was not authorized to speak by name." AP wrote that "the scope of the breach was not immediately clear."
- Fox News (James Cirrone and David Spunt) cites three unnamed sources "familiar with the matter."
- BleepingComputer (Lawrence Abrams), whose "reportedly hacked again" headline carried the story to the security press, relies on CNN's reporting and says the intrusion was reportedly discovered in recent days.
So there are several outlets and at least three separate sets of anonymous sources, all describing an FBI investigation. That is more than one rumor, and it is still not a confirmation.
What the FBI said: nothing. AP says the FBI declined to comment. CNN, Fox and BleepingComputer each say the bureau did not respond. The only on-record remark comes from President Trump on Fox News: "We just heard about it and I will say that it's not good."
Who did it: no one is named, and no group has claimed it. We searched for a leak-site, forum or Telegram claim and found none. This is not an actor's boast; it is an investigation described by unnamed officials.
What is not known
Per every source we read: how the attackers got in, when, whether any records were taken or changed, whether sensitive files were reached, and whether NCIC's availability to officers was affected. AP adds that there is no immediate indication it is related to recent FBI digital outages, which officials attributed to routine upgrades.
Treat anything more specific you read this weekend, a record count, a named group, a sample, as unverified until the FBI or a primary document says it.
What "again" refers to
The "again" is the September breach of the FBI's jobs portal. The extortion group ShinyHunters claimed it took data on nearly all FBI agents and applicants. On October 6 the FBI said the break-in came through a platform run by an outside organization whose contractor missed a security patch. Reuters sources named it as Oracle PeopleSoft, which fits the group's own claim that it used CVE-2026-35273. Arrests followed in the Netherlands and the US. AP also recalls a March FBI disclosure of "suspicious activities" on an internal system.
We covered the September incident twice: our claims ledger on September 29 and the patch and bypass follow-up on October 12 (read next, below). BleepingComputer says there is "currently no indication" that the NCIC incident is linked to ShinyHunters. We are not linking them either.
Am I affected? For police agencies and CJIS security officers
You probably reach NCIC through your state's CJIS Systems Agency, not directly. That shapes what you can check:
- Transaction logs. Ask your state CJIS Systems Agency for your agency's NCIC query and entry log for the last 90 days, by originating agency identifier (ORI) and operator. Look for queries at hours nobody worked, from operator IDs of staff who left or are on leave, bursts of person queries with no case attached, and entries or cancellations nobody remembers making. Ask the state whether it has guidance tied to this incident.
- Accounts and MFA. The CJIS Security Policy has required multi-factor authentication for access to criminal justice information since version 5.9.2, and auditors have been able to sanction a missing MFA control since October 1, 2024. Check that it covers every path: mobile data terminals, records management system logins, remote access and the shared dispatch console account. Remove accounts of departed staff today. Reset any account whose password was ever reused on a personal or vendor site.
- Federal portals. Review recent sign-in activity on any FBI or state law enforcement portal accounts your people hold, and turn on whatever sign-in alerts they offer.
- The follow-on phishing. Incidents like this are a pretext gift. Expect emails and calls that say "FBI CJIS here, we need you to re-validate your NCIC credentials," with a link. Verify by calling a number you already have for your state CJIS Systems Agency or FBI field office, never one in the message.
- Fake emergency data requests in your name. The FBI's own November 2024 notice (PIN 20241104-001) described criminals using compromised police and government email accounts to send fraudulent emergency data requests to US companies, with forum sellers offering "High Quality .gov emails for espionage/social engineering/data extortion." Check your mail logs for messages sent from your domain that your officers did not write, enforce MFA on email, and if you send requests to tech companies, use their law enforcement portals rather than plain email so a spoofed request stands out.
For companies that receive law enforcement requests: the same FBI notice tells you to "apply critical thinking to any emergency data requests," check for doctored signatures and logos, check that the legal codes cited match the requesting authority, and contact the sender and originating authority to verify. Call back on a number you looked up yourself. Urgency ("someone will die unless...") is the lever these requests pull.
For the public: what is in NCIC and what to expect
NCIC holds wanted and missing persons, arrest warrants, stolen vehicles and firearms, and protection orders, and it is used for sex offender monitoring and gun background checks. Protection order records name the people being protected as well as the restrained party, which is why the "what was accessed" answer matters to victims, not only to suspects.
What to expect: possibly nothing, since no data has been reported taken. What not to fall for, whatever happens next: callers claiming to be police or the FBI who say there is a warrant or a record in your name and you must pay, by gift card, wire or crypto, to make it go away. No police department works that way. Hang up and call your local department on its published number. If you hold a protection order and are worried, your local victim advocate or the agency that served the order is the right call.
What our data shows
- No indicators to feed. No source we read published an IP address, domain, file hash or technique. We added nothing to the feed.
- No actor to match. No group is named for NCIC. Searches of our indicator and adversary indexes for "NCIC" and "National Crime Information Center" returned nothing. We do track ShinyHunters, the group behind the earlier FBI jobs portal breach: our indicator index holds a June record of its PeopleSoft CVE-2026-35273 campaign, plus third-party records for its sites. That is context for the September incident, not evidence about this one.
- No edge check. NCIC is not a website anyone reaches from the internet, so our edge instruments would not see an intrusion into it. We did not run one, and we make no first-party claim either way.
Sources
- BleepingComputer, "FBI reportedly hacked again, this time targeting nationwide police database" (November 21): https://www.bleepingcomputer.com/news/security/fbi-reportedly-hacked-again-this-time-targeting-nationwide-police-database/
- CNN, original report (November 20; returned HTTP 451 to our reader): https://www.cnn.com/2026/11/20/politics/fbi-hacked-again-target-crime-database
- Associated Press via Yahoo News, "FBI investigating apparent hack of a key criminal justice information database, AP source says" (November 21): https://www.yahoo.com/news/us/articles/fbi-investigating-apparent-hack-key-163324858.html
- Fox News, "FBI crime database hacked, sources say, in second cyberattack in months" (November 21): https://www.foxnews.com/politics/fbi-probes-second-cyberattack-months-hackers-breach-key-crime-database-sources-say
- FBI Private Industry Notification 20241104-001, fraudulent emergency data requests (November 4, 2024): https://www.ic3.gov/CSA/2024/241104.pdf
- NIST NCCoE, MFA for access to criminal justice information (CJISSECPOL 5.9.2, sanctionable from October 1, 2024): https://www.nccoe.nist.gov/get-involved/attend-events/implementing-multi-factor-authentication-mfa-protect-access-criminal
Read next: The FBI Says a Contractor Missed One Patch. ShinyHunters Is Still Walking Through That Door, Now Spelled /%50SEMHUB/., our October 12 post on how the September FBI breach happened.
Every indicator in this post is in the feed. Free.
1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.