41,000 DHS Records Leaked. Okta Isn't Who Failed.
Hacktivists say they walked out of DHS through its Okta login system Wednesday, Oct. 28. Okta's denial checks out, and the evidence points to DHS's own credential hygiene as the real failure.

Two companies looked at the same breach Wednesday, Oct. 28, and both are probably telling the truth. That's the uncomfortable part.
A hacktivist group calling itself Department of Peace says it walked out of the Department of Homeland Security with records on more than 41,000 employees and contractors. The transparency nonprofit Distributed Denial of Secrets published it as a searchable database called "Icepick," and co-founder Emma Best called it "extraordinary but deceptive in its simplicity as it identifies the officials responsible for overseeing covert and undercover operations, the government's hunt for leakers and the failed BlueLeaks investigation."
The hackers named their entry point: an Okta service that DHS uses for single sign-on. Okta isn't backing down. "Okta is secure, and we have no evidence our data or systems were compromised," a company spokesperson said.
Translation: Okta's own house is clean, and it has no intention of taking the blame for whatever happened inside DHS's tenant.
That denial covers exactly one thing: Okta's own infrastructure. It says nothing about whether a DHS administrator's credentials were phished, whether a session token walked out the door, or whether DHS's Okta configuration left group memberships exposed to anyone with a foothold.
This isn't DHS's first detection failure. Earlier this year, personnel twice dismissed signs of hackers inside the Homeland Security Information Network before confirming a breach. A department that has already missed its own intrusion signals twice in one year is not one you bet on for flawless Okta hygiene the third time.

DHS's own statement doesn't dispute it. "We are aware of a potential breach and are actively working to address the situation swiftly and effectively," the agency said, adding it would update the public "when more information is available." That's the standard holding pattern, not a denial.
Why the Target List Matters More Than the Size
What's different this time isn't the count. It's the precision: the dataset reportedly includes internal group memberships, the exact metadata an identity provider assigns to control which applications a person can open. That reads as a login-directory extraction, not a scraped spreadsheet.
That precision is what should scare federal contractors. If DHS's Okta deployment let an attacker pull group memberships tied to undercover and surveillance work, every agency and contractor running the same SSO pattern has the same blast radius sitting in their own tenant right now, waiting on nobody's patch schedule but their own.
What to watch: whether DHS's eventual statement names a vector (stolen admin credential, exfiltrated token, or misconfiguration) or stays vague past the first news cycle. Silence past 30 days is itself an answer.
- Leak site publishes data on more than 41,000 DHS employees obtained by hacktivists
- DHS personnel leak exposes contact details and sensitive job information
- Leak Website Releases Data on Thousands of US Homeland Security Employees
- Massive Leak Exposes 41,000 Homeland Security Workers
- DHS Okta Data Leak: 41,000 Staff Exposed [2026]
- DHS Employee Data Leak: 40,000 Records Exposed [2026]
- Hacker Behind "Department of Peace" Posts 40,000 DHS Employee Records Online: how 11 outlets framed it
- DHS Data Leak Hits 40,000+ Staff, ICE and CBP [2026]
- Website leaks data on more than 40,000 DHS employees
- Leak website releases data on thousands of US Homeland Security employees - The Korea Times
- Leak website releases data on thousands of US Homeland Security employees
- Leak website releases data on thousands of US Homeland Security employees - OKTA News
- Leak website releases data on thousands of US homeland security employees