Research

USDA Reset Every Database Password After a Security Incident, and Farm Payment and Loan Systems Went Down All Week. What Farmers, Lenders, Agents and Vendors Should Do Now

USDA Reset Every Database Password After a Security Incident, and Farm Payment and Loan Systems Went Down All Week. What Farmers, Lenders, Agents and Vendors Should Do Now

If you farm, lend to farmers, sell crop insurance, or run a system that connects to the US Department of Agriculture, assume for the next few weeks that any email or text about a USDA "password reset," a "payment delay," or "updating your direct deposit" is fake until you have confirmed it yourself. Do not click the link. Go to farmers.gov or fsa.usda.gov by typing the address, or call your county USDA Service Center at the number you already have. Then check that your payment and bank details at USDA have not changed.

Here is why. During the week of November 16, USDA's own security team found what it called a security incident, reset every database password across its environments, and in doing so knocked farmer-facing payment and loan tools offline for days. USDA has not said who was behind it, and the public accounts of whether anything was taken do not agree. Every outage like this is a gift to phishers: people expect to hear from USDA, expect to be asked to log in again, and are worried about money. That is the window to close.

What to do today

Farmers and ranchers

  • Never act on a link. USDA was resetting its own internal database passwords. Nothing in the reporting says farmers need to reset anything. If a message tells you to "verify your account," "reset your login," or "confirm your bank details" to get paid, treat it as phishing. Type farmers.gov or fsa.usda.gov into the browser yourself.
  • Call your county office, not a number in the message. Use the phone number of your local USDA Service Center from a letter you already have, or look it up with the Service Center Locator on farmers.gov or the FSA Office Locator at fsa.usda.gov. (On Friday the farmers.gov locator carried its own notice that it "is experiencing technical issues receiving updates and may not show the most recent information," so if a number looks wrong, use the one on your last FSA letter.)
  • Check your payment details. When systems are back, ask your county office to confirm the bank account on file for your payments is the one you set up. Nobody has reported a changed account. It costs one phone call to rule it out.
  • Do not miss a deadline because of the outage. DTN reports producers have until December 11 to enroll in 2026 ARC/PLC and dairy producers until December 18 for 2027 Dairy Margin Coverage (both Fridays). If you cannot get through online, call or visit the county office and ask them to note that you tried.
  • If you cannot log in, it may be USDA, not you. Do not try passwords over and over, and do not hand your login to anyone who calls offering to "fix" it.

Ag lenders and Farm Credit staff

  • Expect delays on guaranteed-loan paperwork and status checks. Nextgov reports staff could not reach "key client-facing applications" used to check notifications and loan and aid status, and DTN reports outages "specifically in FSA's loan software."
  • Any request to change where a USDA-related payment, guarantee or loan disbursement goes, whether from a borrower, a "USDA official" or a "loan officer," gets confirmed by a call back to a number you already hold. Not a number in the email.
  • Tell your borrowers the same thing in one sentence: USDA will not email you a link to fix your payments.

Crop insurance agents and Approved Insurance Providers

  • Nextgov ties the affected tools to payments between USDA and farmers, and notes that USDA's safety net includes "crop insurance." Expect your policyholders to be confused and to get phishing that uses your agency's name or RMA's. Warn them before the phishers reach them.
  • Confirm any change to indemnity payment instructions by phone with the policyholder.

Vendors and partners with service accounts into USDA systems

  • USDA's internal email says the response was to "reset all database passwords in all environments." If your integration uses a database login or service account into a USDA environment, it has likely been rotated or will be. Expect your connection to break, and get the new credential through your existing USDA contact, never from an inbound email.
  • Rotate your own side too. Any USDA-related credential stored in your systems, scripts, config files or password vaults should be changed and the old one retired, whether or not USDA asks.
  • Check your logs for unusual access with those credentials going back at least to the start of November, and tell your USDA contact what you find.

What is confirmed

These come from three separate lines of reporting, not one. Nextgov/FCW broke it on Thursday, November 19, citing "three people familiar with the matter" and an internal email. DTN reported separately the same evening with an on-the-record USDA official. NBC News followed Friday with two former USDA officials. We could not find a written USDA press release or a notice on farmers.gov about the incident.

  • The incident. An email sent Monday, November 16, by Chris Rottler, acting assistant chief information officer for USDA's Farm Production and Conservation Business Center, said the department's Cybersecurity and Privacy Operations Center "uncovered a security incident" (Nextgov).
  • The password reset. The same email said USDA's Information Services Division had to "reset all database passwords in all environments, and this is requiring us to reset all applications causing outages" (Nextgov).
  • The outages. Nextgov: "The outages have impacted many financial tools used to facilitate payments between the agency and farmers." DTN reports employee outages since Monday "specifically in FSA's loan software" and in NRCS's ProTracts program, "which releases farmer payments," plus its Service Desk mapping software.
  • How long. A Tuesday email obtained by DTN told 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 to "Proceed at your own risk." A technical bulletin dated Thursday said applications "may continue to experience intermittent outages throughout the week" (Nextgov).
  • VPN. By late Thursday afternoon, per one source and a separate notice, "some staff were also experiencing issues with their virtual private network, or VPN" (Nextgov).
  • USDA's on-record word. Richard Fordyce, USDA Under Secretary for Farm Production and Conservation, told reporters in Kansas City the event was a "cyberthreat" and not a "software update." He said "There was no Personally Identifiable Information (PII)" and "No data was lost because the systems that protect against cybersecurity threats worked." On recovery: "Most systems should be back online by close of business today, and if not, we'll work on that over the weekend." FSA Administrator Bill Beam told DTN, "I have heard that there's some outages" (DTN).

The reporting problem

Part of what made this week hard for farmers is that the people who serve them were not told much either. Nextgov reports "High-level department officials also appear to have not been fully keeping USDA staff informed," and that one source "had earlier been given vague information about a possible security breach." DTN reports USDA's press office had not answered its questions or released a statement. As of Friday evening we found no USDA press release on the incident and nothing about it on the farmers.gov home page.

That silence matters for security as well as for patience. When the official channel says nothing, people go looking for answers, and a convincing fake "USDA update" fills the gap. If you work in a county office or an ag business, the most protective thing you can do this week is tell people plainly: USDA will not ask you to fix your account or payments through a link.

What is not known

  • Who did it. Nextgov: "It's not clear who carried out the intrusion or if any data was exfiltrated from systems." No source we read names an actor, a ransomware group, or how anyone got in.
  • Whether data was accessed. The accounts conflict. Fordyce says no PII was involved and no data was lost. NBC News, citing two former USDA officials "with knowledge of the matter," reports "Hackers accessed the Agriculture Department's system that facilitates payments to farmers," which raised "concerns that hackers could access sensitive information." Those two statements can both be true (access without loss), but nobody on the record has said what was reached.
  • Whether any payment was delayed or misdirected. DTN says the outages are delaying loans, payments and conservation work. No source we read reports a payment sent to the wrong account.
  • Why passwords for "all environments." Resetting every database password is what you do when you cannot rule out that one was exposed. It does not by itself tell us that one was.
  • Whether this is connected to the other outages of the week. DTN reports intelligence officials told Congress on Wednesday that the recent outages were "separate incidents associated with maintenance and technical changes." Fordyce's own description of USDA's as a "cyberthreat" sets it apart from that framing. No source ties it to any other incident.

How we know, and what we checked

We read the Nextgov/FCW report, the DTN report and the readable part of the NBC News report directly. The NBC article is partly behind a subscription wall, so there may be detail we did not see. The usda.gov press release page refused our automated read (HTTP 403), so we cannot rule out a statement there; farmers.gov showed only the Service Center Locator notice quoted above. Other outlets carrying the story relay one or more of these three.

We searched our own indicator index for USDA, usda.gov, farmers.gov and FSA lookalike domains. Nothing in it impersonates USDA. The closest hits were unrelated (US Bank phishing, stablecoin lures, malware named for farming games). Indicators: none published in the sources we read, so we added nothing to the feed. There is no CVE or exploit path in this story, so there was nothing for our edge sensors to look for, and we did not scan or probe any USDA system.

If you see a USDA-themed phishing email or text this week, report it to your county office and to CISA at report.cisa.gov, and forward phishing email to [email protected].

Sources

  • Nextgov/FCW, David DiMolfetta and Jory Heckman, "USDA grapples with security breach as IT staff take multiple systems offline" (November 19, 4:42 p.m. ET): https://www.nextgov.com/cybersecurity/2026/11/usda-grapples-security-breach-it-staff-take-multiple-systems-offline/417350/
  • DTN/Progressive Farmer, Jake Zajkowski, "USDA Confirms Cyberthreat on Loan Software Amid Widespread Systems Outages" (November 19, updated November 20): https://www.dtnpf.com/agriculture/web/ag/columns/washington-insider/article/2026/11/19/usda-loan-software-systems-face-amid
  • NBC News, Julia Ainsley, "Agriculture Department breached by hackers, sources say" (November 20, 5:12 p.m. ET): https://www.nbcnews.com/politics/national-security/agriculture-department-breached-hackers-sources-say-rcna610497
  • farmers.gov home page (read November 20): https://www.farmers.gov/

Read next: N-able Confirms a Breached Server in Mail Assure and SpamExperts Hosted Cloud. Mail Still Flows, the Console Is Dark. What MSPs Should Check When It Returns, the same playbook from the vendor side: what to rotate and verify when a service you depend on goes dark after a breach.


Every indicator in this post is in the feed. Free.

1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.

Get your free key → analytics.dugganusa.com/stix/register