Skip to main content
Back to SpamAssist

A clearer next step

Help me choose where to start

Find a verification or recovery playbook

Source-backed U.S. guidance. Start with what happened; you do not need to share a name, account number or code.

A family emergency request: agree on a callback routine

FTC guidance · Reviewed 2026-10-03

Clues to investigate

  • Urgent money request and secrecy
  • A familiar-sounding voice used as proof

A legitimate situation can look similar

Real emergencies happen. A familiar voice alone cannot establish who is calling.

What to do

  1. Pause the payment request and call the person using a number you already know.
  2. If they cannot be reached, contact another trusted relative or friend.
  3. Agree with family in advance to use independent callbacks for urgent money requests.
  4. Ask permission before sharing a redacted summary with your trusted circle.

SpamAssist does not authenticate voices, place calls or monitor family members.

Read the official FTC source
Verify a changed invoice before paying

FBI guidance · Reviewed 2026-10-03

Clues to investigate

  • Changed destination or payment procedure
  • Unexpected executive gift-card request
  • Pressure to bypass approval

A legitimate situation can look similar

A vendor may legitimately change banks. A familiar email thread or matching invoice does not independently confirm the change.

What to do

  1. Hold the changed payment while checking.
  2. Call a vendor contact already on file, independently of this request.
  3. Confirm the destination and change through your normal authorization process.
  4. Record the contact source, date, unanswered questions and second review.

Documents and checklist completion cannot authenticate the sender or authorize payment.

Read the official FBI source
A card payment was sent

FTC guidance · Reviewed 2026-10-03

Clues to investigate

  • Payment followed a deceptive request

A legitimate situation can look similar

A disputed charge alone does not establish fraud.

What to do

  1. Contact the card issuer promptly through its official app or the number on your card.
  2. Explain what happened and ask about refund or dispute options.
  3. Keep redacted transaction records.

The issuer determines available options; a refund is not guaranteed.

Read the official FTC source
A bank transfer, wire or app payment was sent

FTC guidance · Reviewed 2026-10-03

Clues to investigate

  • Transfer to an unexpected recipient

A legitimate situation can look similar

A transfer is not automatically fraudulent.

What to do

  1. Contact the bank, transfer company or payment app immediately through a known channel.
  2. Ask whether reversal or recovery is possible.
  3. Record references privately and avoid recovery-fee offers.

Availability depends on the provider and circumstances.

Read the official FTC source
Gift-card details were shared

FTC guidance · Reviewed 2026-10-03

Clues to investigate

  • Request to send a gift-card number or PIN

A legitimate situation can look similar

Buying a gift card as a gift is different from sending its code to an unsolicited requester.

What to do

  1. Contact the card issuer promptly.
  2. Keep the card and receipt privately.
  3. Ask about a refund.

Do not put gift-card numbers or PINs into SpamAssist.

Read the official FTC source
Cryptocurrency was sent

FTC guidance · Reviewed 2026-10-03

Clues to investigate

  • Demand to deposit crypto to release funds

A legitimate situation can look similar

The payment method alone is not proof of fraud.

What to do

  1. Contact the exchange or ATM operator promptly about the fraudulent transaction.
  2. Ask about available options and keep records privately.
  3. Report what happened through official reporting channels.

Crypto payments can be difficult to recover. Never trust guaranteed recovery.

Read the official FTC source
Credentials or identity information were exposed

FTC guidance · Reviewed 2026-10-03

Clues to investigate

  • Password, code or identity details requested

A legitimate situation can look similar

A code you requested in an official app is different from giving it to a caller.

What to do

  1. Use the service’s official recovery process.
  2. Change exposed and reused passwords; enable two-factor authentication.
  3. Use IdentityTheft.gov for identity-theft guidance.

The right steps depend on what was exposed; no secrets are needed here.

Read the official FTC source
Unsolicited remote access or software

FTC guidance · Reviewed 2026-10-03

Clues to investigate

  • An unsolicited caller requests device access

A legitimate situation can look similar

A support session you arranged with a trusted provider is different.

What to do

  1. End unsolicited access.
  2. Update trusted security tools and scan the device.
  3. Secure affected accounts; get help from the manufacturer or someone trusted.

SpamAssist cannot scan devices or confirm that malware was removed.

Read the official FTC source
Small payouts, then deposits to unlock earnings

FTC guidance · Reviewed 2026-10-03

Clues to investigate

  • Unsolicited task job
  • A small initial payout builds trust
  • A later deposit supposedly unlocks earnings

A legitimate situation can look similar

Payment for real work is different from paying a recruiter or platform to release supposed earnings.

What to do

  1. Stop depositing money to unlock earnings.
  2. Review the sequence of messages, not only the first payout.
  3. If money was sent, contact the provider promptly.

A small payout does not prove the later request is legitimate.

Read the official FTC source
Someone offers to recover money for a fee

FTC guidance · Reviewed 2026-10-03

Clues to investigate

  • Unexpected recovery offer after a loss
  • Upfront fee or guarantee of recovery

A legitimate situation can look similar

Contacting your own payment provider through a known channel is different from accepting an unsolicited recovery offer.

What to do

  1. Do not send an upfront recovery fee or sensitive details.
  2. Independently check who contacted you.
  3. Use official provider and reporting channels.

Reporting and paying for help do not guarantee recovery.

Read the official FTC source
An unexpected support call or alarming pop-up

FTC guidance · Reviewed 2026-10-04

Clues to investigate

  • A pop-up gives a number to call about a supposed virus
  • An unsolicited caller asks for access or payment

A legitimate situation can look similar

Support you requested through the manufacturer’s official website is different from an unexpected caller or pop-up.

What to do

  1. Do not call the number in the pop-up or allow unsolicited access.
  2. Close the warning and contact the manufacturer through a route you found independently.
  3. If access was allowed, end the session and use a trusted device to secure affected accounts.
  4. Contact your payment provider promptly if money was sent.

SpamAssist cannot examine your device or prove it is free of malware.

Read the official FTC source
A new relationship turns into requests for money

SEC / Investor.gov guidance · Reviewed 2026-10-04

Clues to investigate

  • Friendship or romance leads to an investment platform
  • Displayed profits are followed by fees to withdraw
  • Repeated excuses prevent meeting or independent verification

A legitimate situation can look similar

An online friendship alone is not evidence of fraud. Assess the actual requests and what can be independently verified.

What to do

  1. Pause additional payments while independently verifying the request.
  2. Write a redacted timeline of first contact, promises, deposits and withdrawal requests.
  3. Use Investor.gov to research an investment professional, then independently confirm their identity.
  4. If money was sent, contact your provider promptly and avoid upfront recovery-fee offers.

A screenshot of profits, a small withdrawal or an app-store listing cannot establish legitimacy.

Read the official SEC / Investor.gov source
Check the investment professional and possible impersonation

SEC / Investor.gov guidance · Reviewed 2026-10-04

Clues to investigate

  • A registration number is supplied as proof
  • Contact details differ from independently sourced records

A legitimate situation can look similar

Registration can be real while the person contacting you is an impersonator. Registration also does not guarantee an investment’s safety.

What to do

  1. Open Investor.gov independently and search the professional or firm.
  2. Compare the claimed identity with the official record.
  3. Contact the firm through independently verified details, not the message’s link or number.
  4. Keep unanswered questions visible and pause unverified transfers.

SpamAssist does not verify licensing, endorse investments or offer investment advice.

Read the official SEC / Investor.gov source
I selected Allow on an account-permission screen

FBI / IC3 guidance · Reviewed 2026-10-04

Clues to investigate

  • An unexpected file or invitation leads to a permission screen
  • An app asks to read email, files or send messages

A legitimate situation can look similar

A legitimate app can request permissions. Check who operates it and whether the requested access is expected.

What to do

  1. Use a trusted device and the account provider’s official security settings.
  2. Review connected apps and remove access you did not intend to grant.
  3. Review account activity, sessions and email forwarding rules; contact your provider or workplace IT if needed.
  4. Secure exposed credentials separately. Changing a password alone may not revoke app access.

SpamAssist cannot revoke permissions or verify that access has ended.

Read the official FBI / IC3 source
Help someone without blame or pressure

FTC guidance · Reviewed 2026-10-04

Clues to investigate

  • Secrecy or money requests make someone reluctant to discuss a relationship

A legitimate situation can look similar

Disagreeing with a relative’s choice does not establish a scam or give permission to access their accounts.

What to do

  1. Ask permission to look at the request together. Listen before suggesting actions.
  2. Discuss specific requests and independently check facts rather than criticizing the person.
  3. Agree on a pause and a known callback routine for money requests.
  4. Share only a summary they approve with a trusted reviewer.

A family agreement is optional and does not grant account access or decision-making authority.

Read the official FTC source
Choose a trusted contact while keeping control

CFPB guidance · Reviewed 2026-10-04

Clues to investigate

  • Someone demands passwords in order to help
  • An unexpected caller claims to speak for your bank

A legitimate situation can look similar

A trusted contact can support communication. That is different from giving them account credentials or financial authority.

What to do

  1. Choose someone you trust and discuss what help you want.
  2. Ask your bank or credit union about its trusted-contact options through a known channel.
  3. Agree what summaries can be shared and how to request help.
  4. Keep passwords, codes and financial account numbers private.

A SpamAssist circle is not a bank’s trusted-contact designation or a power of attorney.

Read the official CFPB source
Contractors: a supplier or project payment changes

FBI guidance · Reviewed 2026-10-04

Clues to investigate

  • A familiar project thread changes the payment destination
  • An urgent request bypasses normal approval

A legitimate situation can look similar

Project variations and supplier changes can be legitimate; verify the change independently.

What to do

  1. Identify the project, expected supplier and requested change without recording full account numbers.
  2. Call a supplier contact already in your records.
  3. Confirm the amount, scope and destination using your normal process.
  4. Record unanswered questions and a second review; obtain payment authorization separately.

This is a verification template, not approval of a contract, vendor or payment.

Read the official FBI source
Property managers and buyers: changed deposit or wire instructions

FBI guidance · Reviewed 2026-10-04

Clues to investigate

  • Closing or deposit instructions suddenly change
  • An email supplies a new contact number

A legitimate situation can look similar

A scheduled closing can be real while emailed wiring instructions are compromised.

What to do

  1. Pause changed wire or deposit instructions.
  2. Call the established agent, title company or property contact using a number confirmed earlier.
  3. Verify the intended payee and process; follow normal approval rules.
  4. If a transfer was sent, contact the financial institution immediately and report suspected BEC to IC3.

SpamAssist cannot verify ownership, escrow status or wiring details.

Read the official FBI source
Nonprofits: an urgent executive or grant payment request

FBI guidance · Reviewed 2026-10-04

Clues to investigate

  • A leader requests gift-card codes or an unusual payment
  • Secrecy and urgency bypass an organization’s controls

A legitimate situation can look similar

A genuine leader may request purchases; their name in an email does not confirm the request.

What to do

  1. Pause unusual purchases or requests to share gift-card codes.
  2. Contact the leader or finance contact through an established channel.
  3. Check the payee, purpose and normal approval requirements.
  4. Document an independent review before authorized staff decide on payment.

This workflow does not verify grant eligibility or replace financial controls.

Read the official FBI source
Small offices: verify payroll or reimbursement changes

FBI guidance · Reviewed 2026-10-04

Clues to investigate

  • A message requests a new payroll destination
  • The change is urgent or arrives outside the normal process

A legitimate situation can look similar

Employees legitimately update details. Verify through the established HR process before acting.

What to do

  1. Use the existing authenticated HR process or known employee contact.
  2. Confirm the change independently and check normal authorization requirements.
  3. Record the verification source and date without storing banking details here.
  4. Ask a second authorized person to review unresolved questions.

SpamAssist does not process payroll, approve changes or store bank details.

Read the official FBI source
A prize requires a fee or gift-card payment

FTC guidance · Reviewed 2026-10-04

Clues to investigate

  • Pay a fee or supposed tax before receiving a prize
  • A caller demands payment codes or banking details

A legitimate situation can look similar

A promotion can be real, but a prize claim needs independent verification and never becomes reliable just because a caller knows your name.

What to do

  1. Pause payments to claim the prize.
  2. Do not share gift-card codes, passwords or account numbers.
  3. Verify the organization through contact details you found independently.
  4. If you paid, contact the payment provider promptly.

SpamAssist cannot verify a lottery entry or award.

Read the official FTC source
Someone claims to be the government and demands immediate payment

FTC guidance · Reviewed 2026-10-04

Clues to investigate

  • Threats of arrest or loss of benefits
  • Instructions to move money or use unusual payment methods

A legitimate situation can look similar

A real agency may send correspondence. A caller’s name, badge number or caller ID does not establish identity.

What to do

  1. Pause and do not use the unexpected message’s number or link.
  2. Find the agency’s official .gov site independently and use its published contact process.
  3. Keep security codes and banking details private.
  4. Contact your provider promptly if you sent money.

SpamAssist cannot authenticate an agency notice or determine your benefits.

Read the official FTC source

Reading and using guidance stays free. Saving a case uses existing membership rules and requires your confirmation. These are reviewed summaries, not live monitoring or legal advice.

Privacy & site analytics ·