U.S. Department of Agriculture

A USDA cybersecurity incident disrupted applications used for farmer loans, payments and conservation work in November 2026. A senior official publicly acknowledged a cyberthreat Nov. 20 and announced a restoration target, while confirmed completion remained unavailable. Reporting about payment-system access and the official’s denial of personal-data loss leave the full data scope unresolved.
The incident is confirmed to be cyber-related, but the specific attack mechanism is unknown.
Authorized users could not access required data because of the incident, even when the data was not encrypted, deleted, or destroyed.
Internal business, administrative, operational, or staff-facing systems were unavailable.
A specific application or software platform became unavailable or unusable.
VPN, remote desktop, telework, remote administration, or other remote-access capabilities were unavailable or restricted.
The organization could not process, receive, issue, reconcile, or record payments normally.
Staff, customers, patients, students, residents, or other users could not access records or case information normally.
Public administrative, licensing, permitting, court, tax, records, benefits, or other government services were materially affected.
Employees or contractors were unable to perform normal duties because systems, data, facilities, or communications were unavailable.
The incident may involve extortion, but available evidence does not establish which extortion indicators were present.
The U.S. Department of Agriculture experienced a cybersecurity incident that led staff to take multiple applications offline while resetting database passwords and application connections. Nextgov/FCW and Government Executive jointly reported on Nov. 19 that three people familiar with the matter and internal USDA communications documented several days of disruption. DysruptionHub assesses cyber involvement as confirmed because the reporting quotes USDA’s own security-incident wording; the technical intrusion method remains unestablished.
The earliest reported outage began Friday afternoon, Nov. 13, according to Reddit user AngryBagOfDeath, who wrote that service had been down since “last Friday afternoon.” The Nov. 13 date is inferred from the comment captured Nov. 19. Confidence in that timing is low: the account has not been independently verified and does not identify the affected applications. The commenter also said employees had repeatedly been told the issue was routine maintenance. The suggestion that personal information was accessed remains speculation, not evidence of data theft.
A Nov. 16 internal email from Chris Rottler, acting assistant chief information officer for USDA’s Farm Production and Conservation Business Center, linked database-password and application resets to a security incident identified by USDA’s Cybersecurity and Privacy Operations Center. That date establishes an internal notification, not when the intrusion began. A separate Reddit user, therealestboneslicer, said the Farm Service Agency had lacked direct application access since Monday afternoon, Nov. 16. The two accounts may describe different systems or stages of disruption; the Monday account does not rule out an earlier outage. The first identified public reporting is dated Nov. 19. The intrusion start and restoration date remain unknown.
The outages affected financial tools used to facilitate payments between USDA and farmers. Staff also could not access applications used to check notifications and the status of loans and other aid. These are concrete interruptions to agricultural assistance administration. DTN subsequently documented delays to loans, payments and conservation work, without a complete count of affected farmers or quantified losses.
The disruption reflects the operational consequences of the security response as well as the underlying incident. Resetting database passwords required application resets across environments, according to the internal email described by Nextgov/FCW. The evidence does not establish a nationwide interruption to every USDA program, food production, food distribution or nutrition benefits.
DTN’s Nov. 20 update said FSA loan software, NRCS’s ProTracts payment program and mapping services were affected. Undersecretary Richard Fordyce called the event a cyberthreat and expected most systems to return by the end of that day, with work continuing over the weekend if needed. That was a target, not confirmed recovery.
FSA Administrator Bill Beam had acknowledged outages Nov. 19. A Tuesday internal email obtained by DTN warned that apparently returning applications were not fully restored or verified for production use. Continuing application and processing restrictions support active status through Nov. 20.
The first identified public account was Nov. 19 media reporting based on internal notices and interviews. Fordyce initially described system updates. On Nov. 20, he publicly characterized the event as a cyberthreat, according to DTN. That establishes an external-first public cyber characterization followed by an affected-agency acknowledgment.
Confidence is high that the security incident and application disruption occurred: the joint investigation cites three people familiar with the matter and internal USDA communications. The Nextgov/FCW and Government Executive versions reflect the same reporting, not independent corroboration. The full organizational and service scope remains uncertain because no public technical incident report or comprehensive affected-system inventory is available.
Ransomware, encryption and extortion are not established. Data theft remains unresolved. Reuters, citing NBC News Nov. 20, reported that two former officials said hackers breached a farmer-payment system. Their concern about possible access to food-safety and research information does not establish that those other systems or records were accessed. Fordyce told DTN that no personally identifiable information was involved and no data was lost. No public technical finding resolves the full access or exfiltration scope. Staff inability to retrieve loan and aid information establishes an availability effect, not proof that records were stolen or altered.
The public record does not establish the initial access vector, affected database platforms, compromised accounts, intrusion start, actor identity, malware involvement or the scope of any unauthorized data access. The names of all unavailable applications, duration and monetary effect of payment disruption, number of affected users, and final recovery date also remain unresolved.

Nationwide geographic remit of the affected federal department; does not establish disruption to every USDA program or locality.
Washington is the physical headquarters anchor of the affected department. No facility-specific outage is established.
A cybersecurity incident disrupted USDA payment tools and staff access to loan and aid information. Internal notices described database-password resets and application outages; remote-access problems also continued Thursday. Whether payments were delayed, how many farmers were affected, ransomware, data theft and responsibility remained unconfirmed.
“reset all database passwords in all environments, and this is requiring us to reset all applications causing outages”
The commenter said the Farm Service Agency had not had direct access to its applications since Monday afternoon. This is an unverified account of application availability, not confirmation of the intrusion start, ransomware, data theft or affected payment volumes.
DTN’s Nov. 20 update reports Fordyce’s public cyberthreat acknowledgment, affected farm applications and a tentative restoration target. He denied personal-data involvement and data loss.
Reuters reported NBC’s account from two former USDA officials that hackers breached a farmer-payment system. Potential access to other sensitive systems was a concern rather than an established finding; the actor was unknown.
It’s been down since last Friday afternoon. Officially nothing was ever mentioned about a cyber security threat to employees. They kept saying routine maintenance.
Signed-in members can report an error, update, or missing source.