Accenture breach: when a supplier holds your keys
A seller claimed 35 GB of Accenture's code, keys and cloud tokens; Accenture called it an isolated matter. Why a supplier's breach is still yours.
Published · 4 min read

In the week of 6 July, a seller calling itself 888 offered on the hacker forum PwnForums what it said were 35 GB taken from Accenture: source code, Azure access keys and tokens, RSA and SSH keys and configuration files, with a screenshot of what appeared to be a private Azure DevOps repository on an Accenture domain. These are the seller's claims, and the reports did not verify them. In a statement to SecurityWeek, reported on 8 July, Accenture said it was "aware of this isolated matter" and had "remediated its source", with no impact on its operations or service delivery. The list matters to any office with an IT supplier, because code, configuration and keys are what an IT supplier typically holds for its clients.
What was claimed, and what is known
Help Net Security reported that the seller described the haul as "just over 35gb of source codes" and listed Azure personal access tokens and Azure Storage access keys among it. Accenture confirmed the incident to SecurityWeek but gave no detail, and Help Net Security noted that it did not confirm any data had left. How the seller got in, how the data was taken, and whether any personal information was involved were all unclear, SecurityWeek wrote.
Ross Filipek, a security chief quoted by SecurityWeek, put the worry plainly: stolen code, credentials and details of infrastructure can serve as a playbook for later attacks, because firms like Accenture sit close to the systems their clients run on. He also said that not every incident creates a direct risk for clients.
Why a supplier's breach is still yours
Under Section 21 of the Data Privacy Act of 2012, Republic Act 10173, an organisation that controls personal data stays responsible for it after handing it to a third party to process, and must use "contractual or other reasonable means" to keep it protected there. Section 20 adds that the controller must make sure those third parties apply the security the Act requires. The duty to tell the National Privacy Commission (NPC) and the people affected, when sensitive data has probably been taken and serious harm is likely, is the controller's as well. A supplier's incident moves none of that to the supplier.
Keys are a different risk from data, and in one way a worse one. A stolen copy of a database is a loss that has already happened; a stolen key is a door that stays open until somebody changes the lock. If a supplier holds working keys to your cloud accounts, its breach becomes yours the moment someone uses them.
How I hold a client's keys
I am a supplier too, and the systems I build hold staff and member records, so the same questions apply to me. Everything runs in the client's own accounts and on their hosting, not mine, so the client always holds the keys. The code is theirs on final payment, and the data stays in their infrastructure. If personal data is involved, a data processing agreement is in place before I touch anything, which is the kind of contract Section 21 has in mind. My answers to these questions are on the track record page.
Five questions for your IT supplier
- Where do our secrets live? Passwords, cloud keys and access tokens belong in accounts we own, in a password manager or the cloud provider's own store for secrets, not in code, chat or email.
- Are your code repositories scanned for keys, and what happened the last time one turned up?
- If you are breached, how soon will you tell us, and what will you tell us? Put the answer in the contract, so you can meet your own duty to the NPC.
- Who changes our keys after an incident, and how fast? Agree it before there is one.
- Who on your side can reach our systems, and through which accounts? Ask for the list, and remove access when the work ends.
If nobody in the office can say which suppliers hold keys to its systems, that list is the first thing to make. If the systems themselves need replacing, the fit check is where to start.
Sources
- SecurityWeek, Accenture Confirms Data Breach After Hacker Claims Source Code Theft, 8 July 2026
- Help Net Security, Accenture acknowledges security incident following 35GB data theft claim, 8 July 2026
- Lawphil, Republic Act No. 10173
Enrique Lacambra III builds internal business systems from Cainta, Rizal.
Tell me what is broken and I will tell you if it is worth building. A 20-minute call, no charge, and I will say so if you do not need me.
