Perfil Falso

Fake business profiles: how to identify and classify them

branddi · Published on July 10, 2024 · Updated on October 25, 2026

A fake business profile claims to represent an organization or an authorized channel without that relationship. To identify it, compare the claimed identity, internal authorization and observed behavior. A similar name, logo or criticism alone is insufficient: distinguish impersonation, fan accounts, resellers, legitimate branches and compromised official accounts before deciding what action is appropriate.

What makes an account a possible business impersonator?

The central question is the relationship the account claims with the brand. A page can discuss a product without claiming to belong to its manufacturer. Another may describe itself as official support and request a payment on the manufacturer's behalf. Both mention the company, but they raise different issues.

Review the complete presentation: display name, handle, biography, images, posts, messages and contact destinations. Record the specific claim that creates confusion. “Uses our logo” describes a visual element; “claims to be our support team and requests a password” describes observable conduct.

This article proposes a practical screening framework. It does not replace each network's rules or independently establish a legal infringement. Meta's account integrity policy, accessed on October 25, 2026, describes restrictions based on violations and context: https://transparency.meta.com/policies/community-standards/account-integrity-and-authentic-identity/. Finding a similar account is not the same as obtaining a platform decision.

How can you distinguish the main account types?

Use the table as an initial hypothesis. Verify the relationship through a source independent of the account itself, and leave the classification open when information is missing.

• Situation — Distinguishing question — Initial classification
• Account claims to represent the business — Does the responsible team confirm authorization? — Possible impersonation if the relationship is denied
• Fan or commentary page — Is its independence clear and consistent with its behavior? — Independent reference requiring assessment
• Product reseller — Does it identify its own business and actual commercial relationship? — Commercial relationship to confirm
• Local branch or partner — Is this channel currently authorized for this purpose? — Authorized channel or registration issue
• Official account changes behavior — Did known administrators authorize the changes? — Possible compromise of a legitimate account
• Similar name in another industry — Is there a claimed connection or a confusing offer? — Similarity requiring context

These categories are not certificates of compliance. A fan account can publish problematic content, and a real reseller can present a misleading offer. Classify identity and behavior separately rather than using one label to resolve every question about an account.

Which signals matter, and which do not prove fraud?

Relevant signals include claiming to provide official support, reproducing the company's presentation while directing users to an unfamiliar destination, promoting an offer the business has rejected, or requesting credentials on its behalf. Each signal needs the surrounding context of the post or conversation.

Few followers, spelling mistakes, a recent creation date or no verification badge may justify review, but they do not establish fraud. A newly opened branch may have a small audience. An old account can change operators. A professional appearance also requires independent verification.

Do not convert these signals into a confidence percentage without a validated method. Record what was observed, what was confirmed and what remains unknown. “The offer is absent from the commercial calendar” differs from “the commercial owner confirmed the offer was not authorized.” The latter needs an identifiable reviewer and confirmation date.

How can you assess fans, resellers and branches without false positives?

For a fan page, examine whether independence is clear in both presentation and interactions. The word “fan” in a biography does not resolve a private message claiming to collect an official payment. Likewise, criticism does not become impersonation merely because the company dislikes it.

For a reseller, confirm the commercial relationship and the permitted use of materials. Selling a product and operating an official company channel are different conditions. Absence from a partner list does not automatically establish counterfeit goods; an existing relationship does not authorize every presentation.

For a branch, confirm the channel with a known contact rather than relying exclusively on the contact displayed by the account under review. An agency change may not yet appear in the register. For networks, the franchise fake-profile response guide addresses responsibility allocation. This article focuses on classification before that operational work begins.

What if an official account appears to have been compromised?

A compromised legitimate account needs a different response from a separate account created to imitate it. Ask known administrators whether changes to the name, contact details, posts or permissions were authorized. Do not request passwords or authentication codes as part of that confirmation.

Record the history supporting the account's official identity and the changes observed. If administrators have lost access, follow the appropriate security and recovery process. Reporting the company's own account as an imitation may confuse the case and does not restore control.

Keep two questions separate: who should control the account, and what is it distributing now? Protecting users may need to proceed while access recovery remains open. Maintain “possible compromise” until technical confirmation, without attributing responsibility to a former administrator or another person without evidence.

How do you record a classification another person can review?

Create a short record with explicit criteria. Another analyst should be able to understand why the account was referred for action or retained for further verification.

• Record the URL, handle and observation date.
• Capture the relevant affiliation claim and its surrounding context.
• Identify the official channel used as the reference.
• Name the person who confirmed or denied authorization.
• Describe observed behavior separately from the risk hypothesis.
• List missing information and who can clarify it.
• Record the provisional category, owner and next decision.

Preserve context without putting unnecessary personal information into the shared summary. A conversation screenshot may include telephone numbers, identity documents or payment details. Restrict access to the full material and share only what the assessment requires.

Use states such as “under verification,” “relationship confirmed,” “possible impersonation” and “referred for assessment.” An account does not become legitimate because nobody answered an internal query; nor does that silence establish it as fake. Keep the outstanding question visible and set the next review.

How would classification work in a fictional example?

Consider an imaginary retailer called Aurora Home. One page posts product photos and identifies itself as an enthusiast community. Another calls itself “Aurora Home Support” and requests a deposit to release an order. A third belongs to a real branch whose registration is outdated. This example is not a Branddi customer or case result.

The first requires assessment of presentation and content, without an automatic report for mentioning the brand. The second requires confirmation that authorization is absent and preservation of the observed request. The third requires branch verification and a register correction before being treated as an external threat.

If the enthusiast page starts collecting payments on the company's behalf, revisit the classification. Its earlier history does not erase new behavior. Record what changed and which evidence prompted the review; do not delete the previous assessment to make the risk look as though it was always confirmed.

When should classification lead to a report?

Refer a case when documented facts support a basis appropriate to the channel. Impersonation, trademark misuse, copied content and fraud are not interchangeable. They can coexist, but each allegation requires its own supporting evidence.

Instagram's trademark form states that it handles specific trademark complaints rather than other kinds of requests: https://help.instagram.com/contact/230197320740525, accessed on October 25, 2026. Do not choose it merely because it appears in a search about fake accounts.

For execution, use the Instagram profile removal tutorial. When hiring support, review authorization and false-positive handling with the brand protection provider selection guide. A submitted report and a verified removal remain different states.

Which questions commonly arise during classification?

Does using a company logo make every account fake?

No. Assess the claimed relationship, context and applicable authorization. Use of the symbol may require a separate rights assessment, but it does not independently prove that the account presents itself as the business.

Should a criticism page be reported for impersonation?

Criticism alone does not establish impersonation. Check whether the account claims an identity it does not possess. Other content concerns require their own assessment, without changing the basis simply to make a report easier.

Does finding the account prove financial harm?

No. Discovery establishes observed exposure. Financial loss, diverted sales or attributable complaints require additional evidence. Do not present market estimates as the measured outcome of that specific occurrence.

How can Branddi support this assessment?

The Branddi Digital Fraud FAQ, accessed on October 25, 2026, describes identification, evidence organization and support for removal workflows according to the channel, available documentation and strategy. Bring official channels and cases for review to define the scope without assuming guaranteed removal.

The cover image is illustrative and does not identify anyone responsible for a real incident.

Back to blog