If you think your nonprofit has been hacked, the first hour is for cutting off the attacker's access and keeping evidence. Cleanup comes later. Lock the affected accounts, disconnect affected computers from the network, call the bank if money moved, and tell your cyber insurer before you hire outside help.

The steps below follow Microsoft, Google, CISA and FBI guidance, with the notification rules that apply in Washington, DC. Sources were checked on November 18, 2026. This is not legal advice.

What should you do in the first hour?

  1. Stop using the compromised email account to discuss the incident. Use phone calls or a separate channel. Microsoft warns that an attacker may still have access to the mailbox.
  2. Lock the affected account. In Microsoft 365, Microsoft's guidance is to disable the account, or reset its password if you cannot, and revoke its active sign-in sessions. In Google Workspace, Google's guidance is to suspend the user, which resets sign-in cookies and app tokens.
  3. Disconnect affected computers from the network and leave them on. CISA's ransomware checklist says to isolate impacted systems immediately, and to power devices down only if you cannot disconnect them.
  4. If money was sent, call your bank now and ask for a recall or reversal. The FBI's Internet Crime Complaint Center says to contact the originating bank as soon as the fraud is recognized, then file a complaint at ic3.gov with the banking details.
  5. If you have cyber insurance, read the policy's notice clause or call your broker before engaging outside help. Policies often set conditions on notice and on which response firms they pay for.
  6. Write down what you know: who noticed what, when, on which account or device. Take screenshots before anything is deleted.

What should you do in the first day?

Work out how far the attacker got, then close the ways back in.

  • Remove what the attacker left behind. Microsoft's guidance lists sign-in methods the user does not recognize, app permissions, administrator roles, mail forwarding and inbox rules. A password reset does not remove any of these.
  • Check other accounts. Review sign-in logs for the same unfamiliar locations or devices, and reset any account that shared a password with the compromised one.
  • Export the logs early. Microsoft Entra ID keeps most audit data for 30 days, and Google's user log events go back up to six months.
  • Warn the people who received mail from the compromised account, by phone or from a different account, so they do not act on it.
  • Turn on multifactor authentication for every account that does not have it.

Does a DC nonprofit have to notify anyone?

Possibly. D.C. Code 28-3852 applies to any person or entity that conducts business in the District and holds covered personal information, and it sets three duties when that information is breached:

  • Notify each affected District resident in the most expedient time possible and without unreasonable delay.
  • Give written notice to the Office of the Attorney General if the breach affects 50 or more District residents, no later than the notice to residents. The notice cannot wait until the final count is known.
  • Notify the nationwide consumer reporting agencies if more than 1,000 people must be notified.

The Attorney General's guidance says breaches are reported by email to databreach@dc.gov, that data which was encrypted and unusable is not a breach, and that an organization must consult the office before concluding that harm to consumers is unlikely. Its consumer protection office is at 202-442-9828.

Residents of other states are covered by their own states' laws, and grant agreements and contracts often carry their own notice clauses. Bring in a lawyer before sending any notice.

Who should you report a cyberattack to?

  • The FBI's Internet Crime Complaint Center at ic3.gov, for fraud and business email compromise.
  • CISA at cisa.gov/report or 1-844-Say-CISA. CISA's checklist also suggests the local FBI field office for ransomware.
  • The Federal Trade Commission at ReportFraud.ftc.gov, for phishing attempts.
  • The DC Attorney General at databreach@dc.gov, when personal information was exposed.

What should you avoid doing?

  • Do not wipe or reinstall a computer before someone has decided whether it is needed as evidence.
  • Do not delete the attacker's inbox rules or the original phishing email before recording them.
  • Do not send new passwords by email.
  • Do not announce the incident publicly until you know what was accessed.

What should change in the first week?

Use the week after to fix the gap that let this happen and the ones next to it:

  • Multifactor authentication enforced on every account, with stronger sign-in for administrators and finance staff.
  • No shared administrator accounts, and administrator rights only for the people who need them.
  • Backups that have been restored in a test, not only scheduled.
  • A written incident response plan with named roles. Our nonprofit cyber incident response guide covers what belongs in one.
  • A check of where you stand with your insurer. The free Cyber Insurance Readiness Check scores the fourteen controls carriers ask about.

Who can help a hacked nonprofit in Washington, DC?

Four kinds of help exist, and the right first call depends on what you have in place:

  • Your cyber insurer. A policy usually comes with access to a breach response team.
  • Your managed IT provider, if you have one, for containment and recovery.
  • A lawyer, for notification duties and for engaging forensic help.
  • Free helplines listed by CISA for nonprofits and civil society groups, including the Access Now Digital Security Helpline. See CISA's resources for high-risk communities.

ETTE is a managed IT provider in Washington, DC that has served nonprofits and associations since 2002, with CISSP and CISA certified engineers. For managed clients, security incidents carry a 20-minute urgent response objective. Managed detection isolates the affected device or account, we restore from tested backups where data was touched, and we work the written incident response plan with your leadership, including what to tell the board, funders and your cyber insurer, and when.

ETTE's line is 202-345-1965, staffed Monday through Friday, 7 AM to 7 PM ET. If you are not a client, call during those hours and ask for an advisor, or use the contact page. More on how we protect nonprofit data is on the nonprofit data security page, and the steps for a single phishing email are in phishing emails at a nonprofit.

Guidance in this article was checked against Microsoft, Google, CISA, FBI and DC government pages on November 18, 2026. It is general information, not legal advice. Confirm current requirements with counsel and with the agencies before acting.