>
av.Amit VijayanCYBERSECURITY & RESEARCHLet\u2019s connect
Back to the library

Cyber news

Daily Cyber Threat Brief — November 22, 2026: FBI probes apparent hack of national crime database

Thumbnail for: Daily Cyber Threat Brief — November 22, 2026: FBI probes apparent hack of national crime database

Case file — Lead incident: The FBI is investigating an apparent hack of the National Crime Information Center (NCIC), the nationwide criminal justice database used by federal, state and local law enforcement across the United States. The intrusion was first reported by CNN on Friday, November 20, citing two people briefed on the investigation, and confirmed to the Associated Press on Saturday by a person familiar with the matter. The NCIC holds records on fugitives, missing persons, criminal histories, stolen property and other law-enforcement data. The FBI declined to comment. The scope of the breach is not yet clear, and investigators have not said how the attackers got in, who is behind it, or what information was taken. President Donald Trump, asked about it on Saturday, said: "We just heard about it, and I will say that it's not good." The apparent compromise would be the second intrusion involving an FBI system in recent months. Status: under investigation; scope and attribution unknown.

Incident timeline

DateDevelopment
July 23, 2026A flaw is introduced into the Microsoft Entra Connect Health API, later exploited to read tenant metadata and administrator email addresses.
October 14–26, 2026The n0n ransomware group uses compromised Qubole credentials to access customer AWS environments through IAM roles configured for Qubole, stealing 53.9 GB across 30,743 files.
November 9, 2026Microsoft detects the Entra Connect Health API vulnerability.
November 11, 2026n0n claims responsibility for the attack on Qubole, the cloud data analytics provider used by Chase, Visa and Mastercard vendors.
November 16, 2026n0n leaks the claimed Chase, Visa and Mastercard data on its extortion site. Transport for London spots suspicious activity on its Oyster photocard website and takes it offline.
November 17, 2026An unauthorized party uses leaked credentials to access Rackspace Spot between about 00:20 and 22:00 UTC, reading Kubernetes Secrets in customer clusters.
November 18, 2026Rackspace learns of the Spot intrusion from a customer report. TfL emails affected photocard customers that their personal information was accessed.
November 19, 2026Microsoft deploys a server-side fix for the Entra Connect Health flaw.
November 20, 2026Microsoft concludes its investigation and begins notifying affected organizations. CNN first reports the FBI NCIC intrusion. BleepingComputer reports the Chase vendor breach and TfL confirms about 265,000 photocard customers affected.
November 21, 2026The FBI investigation into the NCIC hack is confirmed to the Associated Press. Rackspace announces Spot service is fully restored.

1. FBI probes apparent hack of national crime database

The FBI is investigating an apparent hack of the National Crime Information Center, the database at the heart of day-to-day policing in the United States. CNN first reported the intrusion on Friday, November 20, citing two people briefed on the investigation; the Associated Press confirmed it on Saturday with a person familiar with the matter who spoke on condition of anonymity.

The NCIC is a computerized database of criminal justice information available to local, state and federal law enforcement agencies, holding records on fugitives, missing persons, criminal history data, stolen property and other topics. It is the system officers query during traffic stops, arrests and investigations — which is why even an unscoped intrusion into it is a national-scale incident.

Almost everything else remains unknown. The FBI declined to comment on Saturday. The scope of the problem was not immediately clear, and neither CNN's nor the AP's sources disclosed how the attackers gained access, who was behind the breach, or what information may have been obtained. The apparent compromise would mark the second intrusion involving an FBI system in recent months, and it lands at the end of a week of cyber incidents that have alarmed US officials. Asked about the subject on Saturday, President Donald Trump said in a Fox News Channel interview: "We just heard about it, and I will say that it's not good."

Investigation notes

The reporting is careful to call this an apparent hack: the intrusion is confirmed by sources briefed on the investigation, but no agency has publicly confirmed a breach, and no data has surfaced publicly. There is no attribution, no claimed ransom, and no confirmed exfiltration. That is the honest state of the case file as of this morning — and the questions that matter now are whether NCIC data was copied, whether any of it has been altered, and how the attackers reached a system that sits behind federal law-enforcement access controls. Watch for an FBI statement and for any leak-site claims in the coming days.

2. Vendor breach exposes Chase, Visa and Mastercard customer data

J.P. Morgan Chase has warned that a cyberattack at a third-party service provider exposed customers' personal information and marketing data. Visa and Mastercard separately confirmed third-party incidents of their own. No payment card numbers were stolen, and none of the three companies' own systems were affected — but the ransomware group behind the attack says it walked away with far more than marketing lists.

On November 11, the n0n ransomware group claimed responsibility for an attack on Qubole, a cloud data analytics company owned by Idera that the payment firms' vendors use. Between October 14 and 26, the group says it used compromised Qubole credentials to access customers' AWS environments through IAM roles the companies had configured to grant Qubole access. It claims to have stolen 53.9 GB across 30,743 files directly from Qubole — customer contracts, pricing records, staff and trial-user information and production data — and to hold nearly one petabyte of data from Qubole's customer networks. n0n leaked the claimed Chase, Visa and Mastercard data on its extortion site on November 16.

Chase said the attackers accessed certain marketing data held by those vendors, which may include some customer names and email addresses. Reporting put the exposed Chase data at email addresses and phone numbers of about 16,000 wealthy customers tied to an invitation-only card program. Mastercard said the exposure was a limited amount of email addresses — non-payments information — from a small subset of cardholders in a specific benefit program, and that the exposure has been contained. Visa said the claims are associated with an incident involving a third-party service provider in Asia Pacific, that its systems were not involved, and that no payments data such as card numbers was affected. Qubole did not respond to BleepingComputer's request for comment.

Investigation notes

The pattern here is the supply-chain breach in miniature: the target was not the bank or the card network, but a vendor with standing IAM access into their cloud environments. Compromised vendor credentials plus pre-configured cloud roles did the rest. The gap between what n0n claims (nearly a petabyte of customer-network data) and what the victims confirm (marketing data, a subset of email addresses) is wide, and only the victims' forensic work will close it. The extortion angle also matters: n0n says it contacted Qubole and some affected companies before public reports detailed the attacks, and its demands were ignored — a reminder that the leak on November 16 was the consequence, not the start, of the incident.

3. Microsoft confirms Entra Connect Health flaw was exploited to steal tenant data

Microsoft is warning organizations that attackers exploited a vulnerability in its Entra Connect Health service to gain unauthorized access to administrator email addresses and tenant configuration information. The flaw was introduced on July 23, 2026, detected on November 9, and fixed server-side on November 19. Microsoft finished its investigation on November 20 and began notifying affected organizations.

Entra Connect Health is the cloud service that lets administrators monitor the health, performance and alerts of their on-premises identity infrastructure — sync servers, AD FS farms and domain controllers — through the Entra admin center. According to a security notification sent to admins and shared on Reddit, the flaw in the Connect Health API allowed unauthorized parties to read tenant-level metadata and potentially modify monitoring configurations. Microsoft's investigation confirmed unauthorized read-only access to tenant-level metadata had occurred, though it found no evidence of unauthorized configuration changes.

The exposed information included email addresses of tenant technical contacts and administrator accounts; tenant IDs, display names, initial domain names, country codes and regional information; Microsoft Entra license tiers and directory synchronization status, including whether sync was enabled and the last sync timestamp; and Connect Health onboarding status. The API also returned an expired certificate once used to register Connect Health agents with a Microsoft internal service decommissioned in late 2024. Microsoft says the flaw did not expose user passwords, password hashes, authentication tokens, valid cryptographic keys, on-premises server and Active Directory topology details, or Azure subscription information. No customer patch is needed — the fix was deployed server-side — and Microsoft has published a PowerShell script to help admins see what types of tenant metadata could have been exposed.

Investigation notes

The dates are the uncomfortable part: the flaw lived in the API for 109 days before Microsoft detected it, and a further ten days passed before the fix shipped. Microsoft has not disclosed how many organizations were impacted or who exploited the flaw, and more than a dozen administrators have reported receiving the notification. The stolen data is not credentials — but administrator and technical-contact email addresses, paired with tenant license tiers and sync status, are exactly the raw material for convincing spear-phishing and for follow-up messages impersonating Microsoft about this very incident. Any organization that received the notice should treat its admin contact list as known to an unknown party and brief its help desk accordingly.

4. Rackspace Spot breach let hackers read customer Kubernetes secrets

Rackspace has warned customers that hackers breached its Rackspace Spot cloud platform using compromised credentials, allowing them to deploy unauthorized workloads and access Kubernetes Secrets in customer clusters. The intrusion ran on November 17, 2026, between approximately 00:20 and 22:00 UTC. Rackspace learned of it on November 18 after a customer report, and announced full service restoration on November 21.

According to a customer notification obtained by BleepingComputer, the attackers were able to act as legitimate users in some customer organizations, creating pods in Kubernetes clusters, reading Kubernetes Secrets, and listing nodes and volumes. Kubernetes Secrets store sensitive values such as passwords, authentication tokens and API keys used to reach databases, cloud services and other systems. Rackspace warned that the attackers could have read any Secret stored in an affected user's clusters, as well as any Spot API tokens or refresh tokens held by that user.

Rackspace says it has revoked affected tokens and sessions, removed the unauthorized pods, rotated keys, and strengthened access controls and monitoring. Affected customers have been told to reissue Spot API tokens, replace refresh tokens used in automation, download fresh Kubernetes configuration files, and rotate credentials stored in cluster Secrets — and to review logs for databases, container registries, Git repositories, cloud storage and third-party services dating back to November 17. Rackspace shared indicators of compromise including the IP address 23.224.79.106, the range 23.224.0.0/15, and suspicious Kubernetes pod and object prefixes i1, glm- and probe. The company has not said how many customers were affected or whether customer data was stolen. The breach also caused an extended outage of the Spot administration console, temporarily preventing customers from managing clusters and rotating potentially compromised credentials.

Investigation notes

How the credentials leaked in the first place remains unanswered — Rackspace's notification says only that leaked credentials were used. The console outage compounded the damage: customers could not rotate exposed credentials while the platform was being secured. The real exposure window is wider than the 22 hours of access, because any Secret read on November 17 remains valid until it is rotated. The IoCs are specific and actionable — hunt for the i1, glm- and probe prefixes and the 23.224.0.0/15 range in cluster and egress logs — but the only authoritative answer to "was my Secret read?" is Rackspace's control-plane audit log for November 17.

5. Transport for London confirms 265,000 Oyster photocard customers hit

Transport for London has confirmed that a cyberattack on its Oyster photocard website may have exposed the personal data of around 265,000 photocard customers. TfL spotted suspicious activity on November 16, after customers began receiving emails sent from TfL's own systems asking them to create an account they already had. The photocard website was taken offline while the activity was investigated, and the incident has since been contained.

The compromised details may include names, email addresses, phone numbers, home addresses, dates of birth, and security questions and answers. TfL's current assessment is that no passwords, bank or payment card details, customer journey information, photocard photographs, or copies of supporting documents were accessed — and that the names and dates of birth of children with Zip Oyster cards were not compromised. Affected accounts span Zip Oyster cards for children and young people, 18+ Student cards, 18–25 Care Leaver cards, 60+ London cards, Apprentice cards and Veterans cards. TfL emailed customers believed to be affected on November 18, has informed the UK's Information Commissioner, and is asking all photocard customers to change their password and security question and answer. Existing photocards remain valid for travel.

Investigation notes

The tell-tale sign was the email itself: messages generated from TfL's own systems, not spoofed from outside, asking existing customers to create accounts — a strong indicator the attackers had write access inside the photocard platform, not just a stolen mailing list. TfL has not disclosed how the intruders got in, and has not attributed the attack. This is TfL's second major customer-data incident in two years, after hackers stole data on around 10 million customers in September 2024. The exposed security questions and answers deserve attention: they are the kind of data that fuels account-takeover attempts elsewhere, and customers who reused those answers on other services should change them too.

Exposure watch: Shodan currently shows about 791,000 exposed NetScaler instances, 508,000 exposed FortiGate devices, 119,000 exposed Exchange servers and 12,000 exposed Danfoss devices worldwide — the internet-facing attack surface that incidents like this week's keep drawing on.

Sources

Keep exploring.

All articles