Account Compromised in Minnesota? Plan Your Next Steps.

Plain-English remote cyber recovery support for people and small businesses in Minnesota. Contain the incident first, then secure accounts and plan recovery.

Choose your local page

Towns and cities in Minnesota

Choose the town or city closest to you to continue with the relevant Been Hacked Fix recovery page.

Downloadable checklists

Prepare before a breach and recover in the right order

Use these PDFs to record the information you may need before something goes wrong, then follow the same staged recovery process used on this page.

Home user recovery checklist

For personal email, phones, computers, banking, shopping, social media, Microsoft, Google and Apple accounts.

Business recovery checklist

For Microsoft 365, Google Workspace, staff accounts, websites, shared systems, customer data and incident records.

We record your email address, the checklist requested and the time of your request to manage checklist downloads. This form does not send marketing emails. Read our Privacy Policy.

Top Tips

Lost access to your email?

On a trusted device, create a new email to contact your bank and secure key accounts. Check your old address for known breaches at Have I Been Pwned.

A new address may reduce exposure, but cannot stop every scam.
Check the signs

Recognise the warning signs before changing anything

People and small businesses dealing with hacked email, online accounts, Microsoft 365, websites, social media and devices can be disrupted by one compromised mailbox or reused password. In Minnesota, investigate unfamiliar administrator accounts, security software being switched off and payments or invoices being redirected promptly.

An incident may begin with a convincing call, a fake sign-in page, a supplier invoice, stolen browser credentials or an unpatched device. Write down what each person saw and when it happened. A reliable timeline is more useful than guessing how an attacker got in.

Not sure what to do first?

If you've been hacked, start with our step-by-step recovery checklist. It explains what to secure first, how to protect your email and accounts, what evidence to keep, and what to do next.

Recovery Checklist
Warning signSafe first action
unfamiliar administrator accountsReview recent sign-ins from a clean device.
security software being switched offPreserve the message or rule before removing it.
payments or invoices being redirectedPause payment and verify through a known number.
Files renamed, encrypted or replaced by a ransom noteDisconnect the affected device from networks. Keep the note, contact your IT provider and leave backup drives disconnected.
1

Limit the damage

Disconnect a device if malware is suspected, but do not wipe it. Stop remote-access sessions and suspicious calls. If business email in Minnesota is involved, warn anyone who approves invoices or supplier changes.

2

Use a clean route

Use a separate phone or computer to contact your bank, IT provider and account services. Type known addresses yourself and avoid links in the message that caused concern.

3

Secure accounts

Start with email, Microsoft 365 or Google Workspace, banking, domain names and website administration. Reset unique passwords, review recovery details, remove unknown sessions and enable MFA.

Recovery in Minnesota

Check people, accounts, devices and backups together

An account compromise rarely stays inside one inbox. Attackers may study real conversations, imitate trusted contacts or wait until a genuine payment is due. Review sent items, deleted items, forwarding rules, delegated access, administrator roles and sign-in locations.

Ask staff to report unusual prompts without blame. Tell them which route to use if normal email cannot be trusted. Check laptops, phones and shared computers for unfamiliar browser extensions or remote tools.

Confirm backups exist, are separate from the affected system and can be restored before deleting or rebuilding anything. Keep screenshots, email headers, phone numbers, URLs, bank messages and login alerts.

A practical response plan

If your organisation works across more than one site, check any shared accounts, payment processes and supplier communication routes at the same time. Record each password reset, device isolation and bank call so recovery work is not repeated or missed.

If personal data may have been exposed, assess whether the relevant regulator and affected people need to be told. Check your cyber-insurance terms before taking actions that may affect a claim.

The aim is to regain control, understand the likely exposure and reduce the chance of a follow-up attack. Recovery should leave accounts, devices and working practices safer than they were before the incident.

Report fraud in Minnesota

Use official routes and trusted contact details

If money has moved, call your bank immediately and ask whether a transfer can be stopped or recalled. Report through Minnesota Attorney General consumer and fraud reporting. Use FBI Internet Crime Complaint Center for independent prevention and recovery guidance.

Keep reference numbers and note who was contacted. Reporting does not replace containment. Secure accounts and devices at the same time using a route the suspected attacker cannot monitor.

Questions from Minnesota

Frequently asked questions

What should I do first if I have been hacked in Minnesota?

Disconnect affected devices safely, pause payments, preserve messages and screenshots, then use a separate trusted device to secure important accounts.

Who should I report online fraud to in Minnesota?

Contact your bank immediately if money may be at risk. Use Minnesota Attorney General consumer and fraud reporting for the appropriate official reporting route.

Can Been Hacked Fix support someone in Minnesota remotely?

Yes. Initial containment, account checks and recovery planning can often start remotely. We will explain if a device needs hands-on investigation.

Should I wipe the affected computer or phone?

Not before evidence and recovery options have been checked. Wiping too early can remove useful logs, messages and other evidence.