DHS's Info-Sharing Network Just Got Hacked — Twice

The Department of Homeland Security just confirmed that hackers broke into HSIN — the Homeland Security Information Network — a platform that connects federal, state, local, and private-sector partners to share sensitive-but-unclassified intelligence. The breach, first reported by Nextgov and confirmed by DHS in a statement to BleepingComputer, hit sometime between late May and early June. The attackers targeted HSIN servers and a SharePoint collaboration system, but so far nobody knows who they are, what they got, or whether anything actually left the building. DHS says classified systems were untouched and HSIN remains operational, but it's an unclassified legacy environment — which is government-speak for "we've been patching this thing with duct tape and hope."

What makes this worth paying attention to is the pattern. HSIN had its own breach in 2023 when a contractor's coding error set HSIN-Intel's access permissions to "everyone" instead of a limited group, exposing restricted intelligence from the FBI, the National Counterterrorism Center, and dozens of state and local agencies to tens of thousands of unauthorized users — including foreign nationals. That was a misconfiguration. This time, actual threat actors got in. The timing is especially awkward: the U.S. is currently hosting World Cup matches, and HSIN handles real-time incident coordination, threat alerts, and security planning for events. A breach during a tournament with massive interagency coordination could mean the difference between a quiet embarrassment and a full security review.

Source article image
Source image 1

There's something almost predictable about how government information-sharing networks age. You build them with the best intentions — connect all the agencies, share threat data, coordinate response — and then you forget to lock the doors. The DHS has now had two incidents in roughly three years: one where a single line of code opened the front door, and one where someone walked through it. The question isn't whether HSIN will be patched. It's whether the thousands of agencies that plug in

Source article image
Source image 2
to it actually trust the data flowing through it anymore. If a state emergency manager in Florida or a local fusion center in Arizona pulls intel from HSIN during the World Cup, how do they know it's still reliable? The DHS says the system is operational. The real test will be whether the partners who depend on it believe that.

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

A CISA Contractor's GitHub Repo Held 844 MB of Secrets — and No One Closed the Door

Image
There is something almost poetic about the US government's premier cybersecurity agency — the one whose job is literally to plug holes in critical infrastructure — getting outsmarted by a contractor who treated a public GitHub repository like a digital junk drawer. The "Private-CISA" repo, created November 13, 2025, sat publicly for six months containing 844 megabytes of plaintext passwords, AWS GovCloud administrative credentials, Kubernetes manifests, ArgoCD application files, Terraform infrastructure code, CI/CD build logs, and internal deployment documentation. Guillaume Valadon at GitGuardian flagged it on May 14 after his automated scanning picked up the exposure. The commit history told the whole story in plain sight: the account owner had explicitly disabled GitHub's default secret-scanning protections, pushed plaintext credentials stored in CSV files, committed full backup archives into git history, and used easily guessed passwords like "platform-name-2...
Read more