Alabama Cyber Siege: State Silent on Intricate Hack Attack Details

By Dan Evert, CCNP   Published: 05/19/25   Updated: 10/24/26   2 min read

Alabama Cyber Siege: State Silent on Intricate Hack Attack Details

Alabama’s state government spent much of May 2025 dealing with a cybersecurity incident it said little about. The Office of Information Technology confirmed the event and posted updates, but left out the details people wanted most: how attackers got in, which systems were hit and what was taken.

What Alabama has said

OIT said it detected the event on May 9, 2025, and brought in outside cybersecurity firms. It said some state employee usernames and passwords were compromised and that it had found no evidence that residents’ personally identifiable information was retrieved. Employee passwords were reset.

Local outlets reported that the state had not explained the attack vector or named the attackers. That gap fed speculation. Several observers called for a fuller public account once the investigation allowed it.

States as targets

The Alabama incident fits a wider pattern of attacks on state and local governments, many of which run older systems on tight budgets.

The state’s limited disclosure was not unusual. Agencies often hold back details during an active investigation, both to avoid tipping off attackers and to avoid releasing findings that later turn out to be wrong.

Still, residents who depend on state services want to know whether their data is safe. Clear updates help.

Who might be behind it?

Without an official explanation, theories ranged from financially motivated criminals to state-backed hackers. Alabama did not attribute the incident.

Officials said the incident did not cause major disruptions to state services. On May 20, OIT said the threat had been neutralized.

The state did not say whether a ransom was demanded.

What Alabama and other states can do

Security specialists say states should invest in security, run crisis exercises and set clear rules for reporting incidents.

Transparency helps, too. Detailed accounts of what happened and what was fixed, released once it is safe, build public trust and help other agencies defend themselves.

For other states, the lesson is practical: protect employee credentials, use multi-factor authentication and plan the public messaging before an incident starts.

Stay Current

Newer CyberExperts coverage on this topic

This article still works as background. If you want the current picture, start with the freshest related coverage below and today's brief.

Latest Daily Brief

Friday’s brief: GitLab’s 10.0 fix, then VeloCloud attacks, a poisoned LiteLLM release and PHP2Shell logs to check

The fastest way to catch up on what changed after this article was published.

Read Today's Brief

Dan Evert, CCNP

Dan Evert is a self proclaimed Router Jockey. Dan got heavily involved in networking right out of high school and has never looked back! Dan is giving back by working with high school students to get them involved and interested in Networking and Security.