An Accenture employee hooked their personal Claude Code account into a secure Department of Defense system used by several intelligence agencies, letting Anthropic's coding agent run on a Pentagon network for roughly two months before the access was identified and closed, WIRED reported on Thursday, citing sources familiar with the episode.
According to the report, the agent appears to have sent the contractor's login credentials, passwords and a map of the network to a third-party website that the National Institute of Standards and Technology had already flagged as high risk because of a flaw allowing attackers to inject instructions into AI coding agents, the technique known as prompt injection. WIRED withheld the site's name to avoid exposing the system further, and the source said there is no visibility into whether the service retained the data, calling the exposure "100 percent a national security threat."
The affected environment runs on NIPRNet, the Pentagon's internet-connected network for unclassified traffic. The centralized system involved holds controlled unclassified information, material that cannot be released publicly without review and can cover critical infrastructure, weapons and equipment designs, or the location of radioactive material. The contractor had handed their credentials to the agent so it could automate writing code and spinning up cloud servers, which gave it administrative access and let it bypass the security controls a normal login enforces. Because the agent was also committing code on the employee's behalf, it needed to reach the internet, and that is where the credentials and network map appear to have left the building.
Accenture pushed back. A spokesperson told WIRED the allegations were "thoroughly and independently investigated and found to be without merit," and that the company met its legal and contractual obligations. Pressed for detail, Accenture did not say who conducted the investigation and did not dispute that the episode amounted to an incident. Sources told WIRED that Accenture staff did not treat the matter as severe or urgent, and that the company did not initially report it to the government at all, even though federal contractors are required to report cybersecurity incidents within 72 hours of discovery. A DoD spokesperson declined to discuss the status of its networks.
The episode collides with an existing policy wall. Anthropic's usage policy prohibits using its products to interfere with military infrastructure or to bypass authentication, endpoint protection or monitoring controls without authorization, and the Pentagon designated Anthropic a supply-chain risk in March 2026, a label requiring defense contractors to certify they do not use Claude in their DoD work. WIRED did not say when the agent was active, so it is unclear whether the access began before or after that designation took effect.
Security veterans say the real danger lies downstream. Jake Williams, a former NSA hacker now with IANS, told WIRED that individually unclassified pieces of CUI can become classified once aggregated, and that tools and code are often tested on NIPRNet before being moved to the air-gapped SIPRNet and JWICS networks, meaning a stolen NIPR credential could seed a backdoor that later travels into classified territory. Static application security testing, he noted, is built to catch bugs, not deliberately inserted backdoors. Matt Triner, founder of consultancy Hunter Strategy, said the network map alone is valuable because it shows an intruder where the most sensitive assets sit, and that this is "absolutely one that would need to be reported."
There is no indication attackers reached any classified or top-secret system. But the case lands at the worst possible moment for the industry's agent rollout: the same month enterprises are wiring Claude, Copilot and Codex into production, a top federal contractor's own staff demonstrated how quickly an agent with borrowed credentials becomes an exfiltration channel. The gap between "AI policy" and "AI ops" is now a national security finding, and every CISO running coding agents on sensitive networks will be asked whether their version of this story is different.
Comments (0)
Log in to join the discussion
Log InNo comments yet