The FTC published a short alert on 2026-07-20 aimed at veteran-run small businesses, and its core message is simple: an informed workforce is your best defense against scammers and cybercriminals. The alert is not an incident report and describes no specific breach, theft or service disruption. It is a set of starting points for a conversation with your team, plus one planning item for a data breach.
For readers of this site who deal in exchange, wallet or protocol incidents, the useful takeaway is narrower than the headline suggests. Treat this as general staff-awareness guidance, not as confirmed incident news.
What the alert actually says
The source opens by acknowledging that veterans have worked hard to protect the country, and then turns to veteran-run small businesses and the importance of protections against scammers and cybercriminals (c01, c02). Its stated premise is that an informed workforce is the best defense, and it points to free resources to help begin that conversation with a team (c03).
It also notes that scammers constantly look for ways to steal money and personal information, and frames its suggestions as ways to protect the business, employees and customers (c04).
That framing matters. The alert is guidance, not an announcement of availability, a proposal, an approval or an implementation milestone. Nothing in the claims establishes that a product was launched or that a firm changed its practices.
The three specific suggestions
Within the quoted material, the alert gives three concrete directions. The first is training: employees should be told not to send passwords or sensitive information by email, even when a request appears to come from a manager (c05). This targets a common pattern in which familiarity is used to lower suspicion.
The second is awareness and culture: explain to staff how scams happen, and encourage them to talk with coworkers if they suspect a scam (c06). The emphasis on talking to coworkers is about surfacing doubt early rather than letting one person decide alone.
The third is planning: make a plan for saving data, running the business, and notifying customers if a data breach occurs (c07). The FTC lists those three areas plainly. In practice, saving data suggests backups and running the business suggests continuity during an incident, but those readings are an interpretation, not the alert's exact wording.
How a small team can start
Beyond the alert's guidance, here are practical ways to open the conversation with a team. Set aside part of an existing staff meeting rather than scheduling a separate event. Ask employees to bring one suspicious message they have received recently and walk through it together.
Keep the password rule visible. A short written policy that no password or sensitive information goes out by email, even on a manager's request, gives staff something to point to when a request feels wrong. Make clear that reporting a suspected scam will not be treated as a mistake.
Name one person who receives reports, and note how quickly they will respond. That is an author suggestion, not a claim from the FTC alert.
Building the breach plan
The alert's third area is worth separating from training, because it is about response rather than prevention. A breach plan has to answer three questions: what data is saved and how it can be restored, how the business keeps running while systems are disrupted, and how customers will be notified (c07).
The alert does not provide a template, a timeline or legal detail in the claims available here. What it does establish is that notification is part of the plan before an incident occurs, not something to improvise afterward. For a small business, writing down the three areas and assigning a name to each is a reasonable starting point.
What the source does not say
This guide covers only the points summarized from the FTC alert. The available claims do not establish any incident, breach or service disruption, and they do not provide statistics, software or vendor recommendations, legal breach-notification deadlines, a step-by-step template, or guidance specific to crypto exchange, wallet or protocol incidents.
Readers looking for confirmation of a specific event should not rely on this alert. It is general guidance, and its publication date of 2026-07-20 reflects when it was posted, not the date of any incident.
Where this fits for incident-focused readers
If you are tracking an exchange, wallet or protocol disruption, the staff-awareness advice applies to your own organization but tells you nothing about the status of another firm. Use it to prepare internal reporting habits, and continue to source incident status from the affected party's own notices.
The alert's most transferable point is the culture element: staff who suspect a scam should be encouraged to talk (c06). In an incident, early internal conversation is often what turns a quiet doubt into a report. Label that as interpretation, not a claim.
| Area | Alert's guidance | Status |
|---|---|---|
| Email requests | Do not send passwords or sensitive information even on a manager's request (c05) | Published guidance |
| Culture | Explain scams; encourage coworkers to talk (c06) | Published guidance |
| Breach plan | Save data, run the business, notify customers (c07) | Published guidance |
The alert is short and practical. Its value for a veteran-run small business is as a prompt to act before an incident, not as a record of one.