Steve Miller's Blog

A digital workshop for systems-minded tech commentary.

A Forgotten Test Account With the Password ‘Password1’ Exposed Data on 3,300 People, Mostly Children: How to Find the Dormant Accounts Hiding in Your Own Directory

Two IT security administrators review an access audit binder at a workstation with server racks behind glass

Written by

in

Everyone budgets for zero-days. The breach that UK data regulators just turned into a cautionary tale needed no exploit at all. It needed a test account created in January 2012, a password of “Password1,” and two organizations that each thought the other had a handle on directory hygiene. If you want a real-world case study in dormant test account password security, the UK Information Commission’s Office (ICO) just published two of them from the same incident.

What the ICO Found on Dormant Test Account Password Security

On October 20, 2026, the ICO announced reprimands to two Welsh organizations following a November 1, 2024 ransomware attack: Ogi Networks Limited (ONL), a managed IT service provider, and the Local Government Data Unit – Wales, known as Data Cymru. The two formal reprimands, dated October 14, 2026, address the same breach from both sides of an outsourcing relationship. Data Cymru acted as a data processor for public-sector projects and retained overall control of its network, including the authority to instruct ONL to create or remove accounts. ONL acted as Data Cymru’s IT service provider and sub-processor since 2012.

Here is what the primary sources say on the headline claims:

  • The password really was “Password1” on a 2012 test account. According to the ONL reprimand, ONL created an account named “Test2” on January 13, 2012, inside Data Cymru’s Active Directory to test user access before migrating real users. “Test2” was given the password “Password1.” It stayed in Data Cymru’s directory for more than 12.5 years, and had either remained active since 2012 or been inadvertently reactivated before the attack. Checked against Bitwarden’s password-strength tool, the ICO notes, “Password1” is rated “very weak” and can be compromised in less than a second.
  • The victim count is 3,300 people, mostly children. The sheet headline said “thousands of children’s records.” The ICO’s finding is narrower: “During the attack the personal information of 3,300 people was taken, the majority of whom were children,” tied to “two projects supporting children and families.” Because the ICO counts people rather than records and does not give the exact split between children and adults, I retitled the post to match its wording.
  • No ransomware crew is named. Neither the ICO news release nor the two reprimands—nor The Register’s coverage—name a ransomware group or strain. They refer only to “a ransomware attack” and “the threat actor.”

How a Basic Test Account Became a Full Domain Compromise

The technical chain in the ONL and Data Cymru reprimands is the part every identity administrator should read twice, because every step is a trap that exists in real production networks.

First, an incident response firm hired by ONL found suspicious activity on “Test2” as early as September 20, 2024, and on a second test account, “testtest” (created May 8, 2015), on September 24, 2024. Initial access came through a FortiClient SSL VPN connection using “Test2,” likely via password spraying. Neither test account had administrative privileges. They were basic domain user accounts, which was enough to authenticate to an SSL VPN that lacked multi-factor authentication.

Second, why did a 2012 password survive until 2024? Data Cymru actually had a Group Policy Object (GPO) requiring passwords of at least 15 characters. But as the Data Cymru reprimand notes, “Test2” predated that GPO. Because nobody logged into the dormant account, its password was never changed, so Windows never evaluated it against the newer 15-character policy. Raising minimum password length in Group Policy does not touch existing password hashes in the directory.

Third, why did account reviews miss it? Data Cymru’s reviews were not scheduled or routine—and when it asked for a user list, it only requested members of the “Domain Users” Active Directory group rather than the full contents of Active Directory. After the ransomware hit, a full audit in November 2024 took just over four hours and found eight deprecated accounts, including “Test2,” “testtest,” and a consultant account with administrative credentials.

Fourth, once inside, the attacker moved laterally because the local administrator accounts on three affected systems—a primary domain controller, a file server, and an internal SQL server—all shared the same password set in January 2012 and had never been reviewed since. Breaching one system let the attacker collect local account hashes and authenticate across the others. Before deploying ransomware on November 1, 2024, the attacker exfiltrated 42GB of data from those three servers and encrypted 182.7GB across the file and SQL servers.

Finally, the governance gap was contractual too. Data Cymru lacked a UK GDPR Article 28(4)-compliant sub-processor contract with ONL until April 30, 2025, and had not documented how Active Directory would be monitored or audited. As ICO Head of Investigations David Doodson put it, “The responsibility for these failures did not sit with one organisation alone.”

My Recommendations: How to Hunt Dormant Accounts in Your Own Directory

This section is my opinion and my own operational checklist, not official ICO guidance.

  1. Export the whole directory, never a single group. Query every user object across Active Directory or Microsoft Entra ID, regardless of primary group membership, so accounts outside “Domain Users” cannot hide.
  2. Check PasswordLastSet, not just LastLogonDate. An account whose password predates your current length policy is still protected only by your old rule. Reset or disable every account whose PasswordLastSet is older than your current standard.
  3. Put an expiration gate on test and vendor accounts. Flag any account with “test,” “temp,” “vendor,” or “migration” in its name, or with a non-expiring password, and require project closeout checklists to verify removal.
  4. Enforce MFA on every remote access path. Move VPN authentication to SSO backed by Entra ID or your identity provider, enforce MFA via Conditional Access, and audit exclusion groups so test and service accounts cannot log in interactively from outside.
  5. Eliminate shared local admin passwords. Use Windows Local Administrator Password Solution (LAPS) so every server and workstation gets a unique, rotated local admin password, and keep domain controllers isolated.
  6. Put directory audits in the MSP contract. Specify in writing who runs the quarterly full-directory export and who approves every remaining account.

Picture this hypothetical. Imagine your team raises the domain password policy from eight characters to 16 after an audit. Five years later, an old staging account created for a printer migration—never logged into since—still has its eight-character password and still passes the LDAP filter on a legacy VPN. That is my hypothetical illustration of how policy changes leave legacy holes behind, not a reported customer incident.

The Bottom Line

The ICO notes that Data Cymru’s post-incident audit of Active Directory took just over four hours. Skipping that four-hour job for 12.5 years left a “Password1” test account on the perimeter and exposed data on 3,300 people, mostly children. Spend the four hours on your own directory this week.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *