Hackers breached a system the US Department of Agriculture uses to send payments to farmers this week, two former USDA officials told NBC News, which reported the breach on Friday 20 November. USDA has not confirmed the breach, and the department did not immediately respond to a request for comment. The same day, a senior USDA official stood in Kansas City and called the event a “cyberthreat”, insisted no personal information was involved and no data was lost, and said most systems should be back by Friday evening. Both accounts can be true at once. NBC’s sources named the system the hackers reached, but neither side has said precisely what data inside it was accessed, if any.
The systems at the centre of the story have faced outages since Monday 16 November. Farm Service Agency loan software, the Natural Resources Conservation Service program that releases farmer payments, and mapping software used by local offices were all affected as USDA reset database passwords across all its environments, according to the internal email that disclosed the incident. The department’s security operations center had uncovered a security incident, and the reset that followed is what took the applications down.
USDA’s press office has issued no statement. The Cybersecurity and Infrastructure Security Agency referred questions to USDA, which did not immediately respond to a request for comment.
What farmers are facing right now
The outage hits the machinery farmers depend on for money. The Farm Service Agency handles farm loans and support and disaster-relief payments. Its loan software has faced intermittent outages since Monday, according to DTN, along with the Natural Resources Conservation Service’s ProTracts program, which releases farmer payments, and the Service Desk software the conservation service uses to map projects. Staff have been unable to reach the applications they use to check loan and aid statuses, and some were also having trouble with the department’s virtual private network by Thursday afternoon.
Two deadlines now hang over the outage. Producers have until Friday 11 December to elect and enroll in the 2026 Agriculture Risk Coverage and Price Loss Coverage programs, and dairy producers have until Friday 18 December to enroll in the 2027 Dairy Margin Coverage program. From Saturday 21 November, that is 20 days to the first deadline and 27 days to the second. The deadlines have not moved, and no source has said they will.
On Friday, Under Secretary Richard Fordyce said most systems should be back online by close of business that day, and if not, the department would work on it over the weekend. As of writing, no confirmation has appeared that the systems are fully back. An internal email sent on Tuesday warned staff that while some applications “may appear to be coming back online”, they “have not yet been fully restored or verified for production use” and told them to “proceed at your own risk”.
Two accounts of the same week
The reporting splits into two accounts that need to be read side by side, because the gap between them is the story.
| NBC News, 20 November (two former USDA officials) | USDA Under Secretary Richard Fordyce, 20 November (on the record) | |
|---|---|---|
| What happened | Hackers breached the system USDA uses to send payments to farmers this week | A “cyberthreat”, and not a “software update” |
| What was reached | The former officials described the payments database as the known extent of the intrusion so far | “There was no Personally Identifiable Information (PII). No data was lost because the systems that protect against cybersecurity threats worked” |
| What the former officials warned | The former officials warned the compromised system could provide a backdoor to more sensitive information, including food safety data and research on animal-borne illnesses | “Most systems should be back online by close of business today, and if not, we’ll work on that over the weekend” |
| Who did it | Not known | Not stated |
The two accounts do not contradict each other directly. Access without loss is possible: hackers can reach a system without taking data from it. But nobody on the record has said what data, if any, was reached inside that system, and nobody has said how the hackers got in. The department told employees about the incident on Thursday, according to the two former officials who spoke to NBC. Fordyce was speaking about the incident as USDA understood it on Friday; the department has issued no written statement. The actor, the entry method and the full scope remain unknown.
How the week unfolded
| Date | What happened |
|---|---|
| Mon 16 Nov | USDA’s Cybersecurity and Privacy Operations Center uncovers a security incident. Acting assistant chief information officer Chris Rottler emails staff that all database passwords must be reset in all environments, taking applications offline. Outages begin in FSA loan software, NRCS ProTracts and Service Desk mapping. |
| Tue 17 Nov | An internal email warns staff that applications coming back online “have not yet been fully restored or verified for production use” and to “proceed at your own risk”. |
| Wed 18 Nov | Intelligence officials tell Congress that the week’s technology outages were separate incidents tied to maintenance and technical changes, not a coordinated attack. |
| Thu 19 Nov | Nextgov/FCW and Government Executive report the incident publicly, at 16:42 ET. FSA Administrator Bill Beam confirms the outages to DTN. A Government Accountability Office report finds USDA and the Food and Drug Administration had only partially met or not met five of 16 federal cybersecurity requirements for the food and agriculture sector. USDA told employees about the incident on Thursday, according to the two former officials who spoke to NBC. |
| Fri 20 Nov | Fordyce speaks on the record in Kansas City. NBC reports that hackers breached the payment system. DTN updates its reporting with Fordyce’s remarks. |
| Sat 21 Nov | No USDA statement, no CISA statement, and no confirmation that the systems are fully restored. |
The incident landed the same week as the Government Accountability Office report. The report found the agencies had met most of the cyber-related aspects of 16 requirements under the Fiscal Year 2021 National Defense Authorization Act, but had only partially met or not met five of them, in information sharing and emergency preparedness. DTN reported that USDA disagreed with the recommendations and asked the GAO to remove or redirect them, and USDA officials told the GAO there were no plans for further cyber exercises based on potential cyber incidents in the food and agriculture sectors. Fordyce had no comment on the report.
One thing the week did not produce is a link to anything else. Intelligence officials told Congress on Wednesday that the recent outages affecting government and private-sector systems were separate incidents. No source ties USDA to any other incident this week, and this article does not either. TechReview covered the NSA’s classified network outage this week; there is no evidence connecting the two.
This is not the 2006 breach
Search results are currently surfacing two USDA incidents at once. The June 2006 breach is a different, 20-year-old event, and the two should not be mixed up.
| June 2006 | November 2026 | |
|---|---|---|
| What happened | A hacker broke into Agriculture Department systems during the first weekend in June | The security operations center uncovered a security incident; the department reset all database passwords |
| What went down | An Office of Operations workstation and two servers were targeted; the compromised system was taken offline | Numerous farm-program applications offline for days |
| Data at risk | About 26,000 current and retired employees and contractors in the Washington, D.C. area; names, Social Security numbers, photos, building locations | Unknown; whether anything was taken is contested |
| Who was hit | Current and retired USDA employees and contractors | Farmers’ loan, payment and aid systems |
| Disclosure | First public report 22 June, about 20 days after the incident; one year of free credit monitoring offered | Internal email Monday; public Thursday, about three days later; no USDA statement yet |
| Resolution stated | USDA said on 13 July 2006 that personal identity information was not downloaded or transferred outside its computer system | None yet |
June 2006 figures are from reporting at the time, principally Nextgov/FCW, June to July 2006.
By our calculation, three calendar days passed between the internal email on Monday 16 November and the first public reporting on Thursday 19 November. The disruption itself ran at least four days by Friday 20 November, when Fordyce spoke. The 2006 incident took about six weeks to reach a public statement that personal identity information had not been downloaded or transferred; the 2026 incident has had no such statement yet.
What should farmers do while the systems are down?
Do not wait for the systems to come back on their own. The December deadlines still stand, no extension has been reported, and the practical move this week is to reach your county office directly. The steps below are what to try.
- Call your county FSA office about any pending loan or payment, and ask them to note your attempt.
- Visit the office in person if the phone lines are busy, and take your loan and program paperwork with you.
- Treat any message asking you to log in to fix a payment as suspect, and call the office instead.
- Write down every loan number, payment reference and confirmation you already have before the systems return.
- Check the bank account on file for your payments with the county office once the systems are back.
- Do not reset any password or account yourself; the reset was USDA’s internal systems, not farmer accounts.
What to watch next
Whether USDA confirms the systems are fully restored, and when. Whether USDA issues a written statement, and whether it addresses NBC’s report that hackers reached the payment system. Whether CISA says anything at all; so far it has only referred questions to USDA. Whether any payment was sent to the wrong account; delays to loans, payments and conservation work have already been reported, but no misdirected payment has. Whether the 11 December and 18 December deadlines move, or USDA gives farmers hit by the outage more time. And whether USDA acts on the five requirements the GAO report found only partially met or unmet.
This article will be updated as USDA confirms more, or as further reporting emerges about the incident.


