By NHI Mgmt Group Editorial TeamBased on ZeroFox: “One Organization, Five Scams: What a Real Impersonation Case Reveals About Fundraising Fraud” (October 1, 2026)

TL;DR: Trusted brands are being cloned through lookalike domains, fake executive profiles and counterfeit donation pages that move money, credentials and trust, according to ZeroFox, while FTC data cited in the article puts imposter-scam losses at $3.5 billion in 2025. Brand protection now depends on faster discovery, better validation and coordinated disruption, not just domain registration.


At a glance

What this is: This analysis shows how impersonation campaigns use trusted brands, executive identities and fake donation infrastructure to defraud audiences across social, email and web channels.

Why it matters: It matters because fraud operations increasingly overlap with identity governance, exposure management and takedown workflows, especially where public-facing leaders, official accounts and customer trust are the attack surface.

By the numbers:

  • Consumers lost $3.5 billion to imposter scams in 2025, the fifth consecutive year they ranked among the most-reported fraud categories.

Context

Fundraising scams are a trust abuse problem, not just a payment fraud problem. Attackers borrow a legitimate organisation’s name, urgency and public visibility to make victims act before they verify the channel, and the same pattern appears in banking, retail and executive impersonation. Where fraud and cyber convergence is weak, these campaigns outpace ownership, evidence sharing and takedown coordination.

The article’s central point is that impersonation now works as a multi-channel fraud operation. Domains, social profiles, crowdfunding pages and messaging channels reinforce one another, which means defenders have to treat brand abuse as an ecosystem rather than a single fake page.


Key questions

Q: How should organisations respond when their brand is being used in impersonation fraud?

A: Treat it as a cross-functional incident involving fraud, security, communications and legal teams. Prioritise evidence collection, map the full impersonation surface, and use one escalation path for domains, profiles and payment pages. The goal is not only removal of the fake asset, but also stopping reuse across channels and reducing the credibility that made the scam work.

Q: Why do lookalike domains and fake executive profiles work so well in fraud campaigns?

A: They exploit trust shortcuts. Victims rely on brand recognition, urgency and familiar visual cues instead of verifying the channel end to end. When the fake identity is consistent across web, social and messaging, it becomes easier for attackers to create a believable story than for users to challenge it, especially under time pressure.

Q: What are the best practices for reducing impersonation risk across social and web channels?

A: Register high-risk domain variants, claim and verify official accounts, publish a clear verification page, and build a fast reporting path for the public and internal teams. Those measures work best when they are paired with monitoring and a takedown process, because prevention alone will not catch every fake asset that appears.

Q: How do security teams know if impersonation detection is actually working?

A: It is working if high-risk requests are consistently challenged, blocked, or escalated when the claimant cannot satisfy stronger proofing controls. Teams should look for reduced success rates on password resets, MFA bypass attempts, and account recovery requests that originate from unmanaged or suspicious channels. If support agents still rely on familiar questions alone, the control is not effective.


Technical breakdown

How lookalike domains and spoofed channels build false legitimacy

Lookalike domains work because users rely on visual similarity and brand familiarity rather than strict validation of every character in a URL. Once the fake domain exists, attackers can attach payment pages, login forms or donation flows to it and make the destination appear operationally credible. The same logic applies to spoofed social accounts and messaging channels: the identity signal comes from the brand veneer, not from any real trust anchor. That makes the threat partly technical and partly behavioural, because the scam succeeds when the victim transfers trust from the brand to the attacker-controlled surface.

Practical implication: Treat domain similarity, account provenance and payment destination as one verification problem, not three separate reviews.

Why executive impersonation is a credentialless identity attack

Executive impersonation does not require compromise of the executive’s real account. Attackers assemble authority from public photos, titles, social posts and brokered personal data, then use that synthetic identity to increase response rates in donation, job and investment scams. In identity terms, this is an abuse of reputation rather than authentication. The defender’s problem is therefore not password theft but identity proofing of outward-facing claims. The same pattern can also pull in non-human identity exposure when public data on domains, social handles or organisational contacts gives the fraud campaign more believable infrastructure. See the Fraud and Cyber Convergence Guide.

Practical implication: Assume a convincing public profile can be fabricated without account compromise and verify identity claims through independent channels.

How fragmented platforms slow fraud disruption

Impersonation campaigns survive because enforcement is distributed across registrars, social networks, crowdfunding platforms, messaging apps and search providers. Each platform has its own evidence threshold, abuse process and response time, so the defender must correlate signals before any one channel will act. That creates a governance problem as much as an operational one: without shared ownership, evidence packaging and escalation paths, the team sees fragments but cannot prioritise the full threat. In effect, the attacker benefits from the defender’s organisational seams.

Practical implication: Build one evidence and escalation workflow that packages domains, profiles and payment destinations for simultaneous takedown requests.


Threat narrative

Attacker objective: Steal money and trust at scale by making a counterfeit identity look like the legitimate organisation.

  1. Entry begins with a trusted brand being cloned through lookalike domains, spoofed social accounts and fake executive profiles.
  2. Credential and trust abuse follow when victims accept the fake identity, click through to counterfeit pages or engage with fraudulent outreach.
  3. Escalation occurs as the same brand cover is reused across donation scams, fake jobs and money-mule recruitment, expanding reach and credibility.
  4. Impact is monetary loss, reputational damage and the conversion of ordinary supporters into unwitting participants in fraud.

Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.


NHI Mgmt Group analysis

Impersonation fraud is now a trust infrastructure problem, not a single-scam problem. The article shows attackers combining domains, social profiles, payment destinations and executive names into one coordinated abuse chain. That means the control gap is not only detection, but also ownership of the full impersonation surface across teams and platforms. Practitioners should treat brand trust as an attack surface that must be inventoried, monitored and governed.

Executive identity has become a reusable fraud primitive. Public-facing leaders are now being mined for names, photos and context that can be recombined into convincing scams. This is where identity verification and fraud governance intersect: if an organisation cannot distinguish authentic outward-facing identity from synthetic identity, the attacker wins before any technical control is engaged. The right lens is identity assurance, not just content moderation.

Brand impersonation should be handled as a form of non-human identity abuse when infrastructure is the payload. Lookalike domains, counterfeit pages and fake channels behave like rogue, attacker-controlled service surfaces that borrow organisational authority. That makes the overlap with deepfakes, social engineering and AI impersonation more than cosmetic, because the same trust failure drives both human and machine-mediated fraud. Practitioners should align brand protection with identity governance, not leave it isolated inside communications or legal teams.

Impersonation fraud is a convergence use case for fraud and cyber operations. The article reinforces that domain abuse, social impersonation and payment fraud need shared signals, shared triage and shared disruption criteria. Separate queues create delay, duplicate effort and blind spots. Practitioners should organise around the fraud path, not the platform boundary.

From our research library:

What this signals

Impersonation defence is a governance problem as much as a detection problem. Teams that only monitor for fake pages will keep chasing symptoms. The stronger model is to connect domain control, executive exposure management, fraud reporting and takedown evidence into one operating picture so that a fake can be suppressed before it scales.

Brand abuse now behaves like an identity supply chain. Attackers assemble a coherent fraud story from many small assets, including names, photos, domains and payment routes, then reuse that composite identity across campaigns. That means programme owners should think in terms of chain disruption, not isolated incident response.


For practitioners

  • Map your impersonation surface Inventory the domains, social handles, executive identities and payment endpoints that could be abused to impersonate your organisation, then assign owners for each surface.
  • Publish an official channels page Create a single verification page that lists your legitimate domains, social accounts and donation or payment destinations so audiences can self-check before acting.
  • Reduce executive data exposure Limit the personal information available through public profiles and data brokers so attackers have less material to build believable fake executive accounts.
  • Pre-stage takedown evidence packets Prepare standard evidence bundles for domains, accounts and payment pages so reporting and disruption can begin quickly when a fake appears.

Key takeaways

  • Impersonation fraud exploits trust, not just technology, by borrowing legitimate brand signals to make false donation, payment and outreach flows look real.
  • The article shows how domains, social profiles and executive identities can be combined into a single fraud campaign that spreads across channels quickly.
  • The most effective response is coordinated governance across fraud, security and communications, backed by monitoring, evidence packaging and rapid disruption.

Related NHI Mgmt Group resources: Fraud and Cyber Convergence Guide · Deepfakes, Social Engineering and AI Impersonation Guide · Authorised Push Payment (APP) Fraud Guide · Phishing Guide


Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

OWASP API Security Top 10 and MITRE ATT&CK address the attack surface, NIST CSF 2.0 and CIS Controls v8 set the technical controls, and GDPR defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
OWASP API Security Top 10API10 — Unsafe Consumption of APIsFraud campaigns increasingly exploit web and platform trust boundaries that accept unverified external inputs.
Recommendation — Validate externally supplied identity and payment data before consuming it in customer or donor workflows.
NIST CSF 2.0PR.AA-05 — Access Permissions, Entitlements and AuthorizationsOfficial account and domain control depend on accurate authorisation over public-facing identity assets.
Recommendation — Assign and review ownership for public brand assets under PR.AA-05 so impostors cannot act unchallenged.
GDPRArt.32 — Security of ProcessingThe article highlights exposed executive data and PII used to build convincing fake profiles.
Recommendation — Limit public exposure of personal data and apply Art.32 safeguards to reduce impersonation-enabling disclosure.
CIS Controls v8CIS-5 — Account ManagementVerified social and executive accounts are central to reducing impersonation risk.
Recommendation — Use account-management controls to verify, inventory and protect all official public-facing identities.
MITRE ATT&CKTA0006; TA0010 — Credential Access; ExfiltrationThe campaign aims to harvest trust, money and possibly credentials through impersonation-driven interaction.
Recommendation — Map impersonation-driven fraud activity to credential access and exfiltration behaviours during threat hunting.

Key terms

  • Impersonation Fraud: Impersonation fraud is deception in which an attacker poses as a trusted person, organisation, or authority to trick a victim into sending money, credentials, or data. Defenders should verify identity through separate channels, train staff to challenge urgency, and monitor changes to payment instructions, contact details, and account recovery requests.
  • Lookalike Domain: A lookalike domain is a web address designed to resemble a trusted brand closely enough to trick users into believing it is legitimate. In identity attacks, the domain becomes part of the deception layer, letting attackers capture credentials, identity details, or payments through a counterfeit flow.
  • Brand impersonation fraud: A fraud pattern in which attackers mimic trusted organisations to trigger urgent action, capture credentials, or collect payment data. The technical risk sits at the intersection of identity verification, channel assurance, and user trust, which is why security and fraud teams both own the response.
  • Takedown Workflow: A takedown workflow is a controlled process for validating impersonation, capturing evidence, escalating review, and requesting removal from a marketplace or hosting provider. It matters because enforcement quality depends on documentation, traceability, and cross-team coordination.

Deepen your knowledge

The NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, secrets management and machine identity security. It helps practitioners connect identity control to broader security operations and trust abuse scenarios.
NHIMG Editorial Note
Published by the NHIMG editorial team on October 22, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org