← Back to Skills Marketplace
kostja94

brand-protection

by Kostja Zhang · GitHub ↗ · v1.0.1 · MIT-0
cross-platform ✓ Security Clean
95
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install brand-protection
Description
When the user faces brand impersonation, fake websites, phishing sites, or trademark infringement. Also use when the user mentions "fake site," "impersonatio...
README (SKILL.md)

Strategy: Brand Protection

Guides discovery, reporting, and prevention of brand impersonation—fake websites, phishing sites, trademark infringement, and domain squatting. See domain-selection for defensive domain registration; trust-badges for official site verification signals; about-page for identity declaration.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for brand name, official domain, and key assets.

Identify:

  1. Impersonation type: Fake website, phishing, trademark misuse, domain squatting
  2. Evidence available: Screenshots, URLs, WHOIS, hosting info
  3. Legal assets: Registered trademark, copyright ownership
  4. Impact: Traffic interception (fake site ranks for brand queries)? Payment fraud (users pay on fake site, then contact official support)?

Evidence Collection Checklist

Item Action
Full URLs Document all key pages of the fake site
Screenshots Homepage, product pages, logo, layout; include date/time
Comparison Side-by-side: official vs fake (layout, logo, copy similarity)
WHOIS Use ICANN Lookup for registrar, creation date, registrant
Hosting IP lookup to identify hosting provider

Reporting Channels (Priority Order)

Channel Entry Use Case
Domain registrar Abuse / Report Misuse on registrar site Brand impersonation, trademark, fraud
Hosting provider Same; submit abuse form Hosting infringing content
Google Safe Browsing Report Phishing Phishing / impersonation risk
Google Trademark Trademark Complaint or [email protected] Trademark infringement in search; requires registered trademark
Bing Content Removal Content Moderation Platform Copyright/trademark; content removal from Bing
Payment processors PayPal Resolution Center, Stripe support If fake site accepts payments; report fraud
Social platforms X, Facebook, Instagram abuse forms If fake site is promoted or linked there
Google Ads / Microsoft Ads Platform trademark complaint forms If impersonator runs brand ads
DMCA To hosting provider Copyright infringement; images, copy, design copied
ICANN DNS Abuse complaint If registrar does not respond within reasonable time

Report content: Include full URL, clear description of fraudulent activity, and all evidence (screenshots, logs).

Reporting Best Practices

Registrar vs hosting: Use ICANN Lookup for registrar. For hosting, use IP lookup (HostingCheckerOnline, HostingDetector, ipinfo.io) to find origin server—registrar may be Cloudflare while origin host is elsewhere; report to both.

Cloudflare as registrar: Use abuse.cloudflare.com or abuse form; select "Phishing & Malware" for impersonation. Email complaints are generally not processed; use the online form. Provide specific URLs of infringing pages.

Hosting detection: Sites behind Cloudflare CDN hide origin IP. Use reverse IP lookup or hosting detection tools to identify underlying host; submit abuse to that provider as well.

Parallel reporting: Submit to registrar, host, and Google Safe Browsing simultaneously; do not wait for one before others. Google trademark review takes 1–8 weeks.

Legal Options

Option When Notes
Cease and desist Trademark infringement Lawyer-drafted; often first step
DMCA takedown Copyrighted material copied Images, copy, design; hosting providers typically comply
Consumer protection Scam / fraud FTC ReportFraud.ftc.gov (US)
Law enforcement Financial loss, identity theft IC3 (FBI) for cybercrime

Prevention Measures

Defensive Registration

  • Register brand+ai, brand+app, brand+official, etc. See domain-selection for defensive registration.
  • Redirect variants to main domain; do not deploy separate sites.

Official Site Verification

Place "Official website: [domain]" prominently:

  • Homepage (above fold or hero)
  • Sign-in / Sign-up pages
  • Pricing / Payment pages: "Only pay at [official-domain]. Do not enter payment on other domains."
  • Footer: "© [Brand]. Official site: [domain]"
  • FAQ: "How do I verify I'm on the official site?" → "The only official URL is [domain]. Any other domain is not affiliated."

Use trust-badges for verification signals. See about-page for identity declaration.

Customer Support (Payment Fraud)

When users report "can't use after payment" but no record exists—likely paid on fake site:

  1. Verify source: Ask which URL they used (request screenshot or URL).
  2. Response template: Explain that the only official site is [official-domain]; if they paid elsewhere, that site is not affiliated. Recommend: (a) dispute charge with payment provider, (b) use only [official-domain] going forward.
  3. Roll out template to support team; ensure consistent messaging.

User Education

  • Social media pinned post / announcement: "Only use [official-domain]"
  • Email signatures, support replies: link to official domain only

Traffic Recovery (When Impersonation Intercepts Search)

Tactic Purpose
Brand search ads Run Google Ads and Microsoft Ads on brand terms; ensure official site appears first for brand queries
SEO Strengthen official site for branded queries; Organization schema, clear H1, meta tags. See schema-markup, title-tag
Social Pinned post: "Only use [official-domain]. Beware of impersonation."

Monitoring (Ongoing)

  • Periodic search: brand name + common variants (e.g., brand+ai, brand+app)
  • See brand-monitoring for monitoring setup, tool selection, and cadence

Timeline (Typical)

Phase Focus
Immediate (Days 1–3) Support template; site declaration; evidence collection
Short-term (Week 1–2) Abuse reports; Google Safe Browsing; DMCA if applicable
Traffic (Week 2+) Brand ads; SEO; social announcement
Ongoing Monitoring; defensive registration if feasible

Implementation Checklist

Short-term (1–2 weeks): Evidence collection; abuse reports to registrar and host; Google Safe Browsing report; DMCA if applicable; add "Official website" on site.

Medium-term: Add impersonation guidance to domain-selection; official verification to trust-badges, about-page.

Long-term: Periodic search (brand + variants); brand monitoring (BrandShield, Doppel); defensive registration of variants.

Output Format

  • Evidence package (checklist, evidence list)
  • Report templates (registrar, hosting, Google)
  • Timeline (immediate vs medium vs long-term actions)
  • Prevention (defensive registration, site verification, user education)

References

Related Skills

  • domain-selection: Defensive domain registration; brand variants
  • rebranding-strategy: When rebranding, sync brand protection checks
  • brand-monitoring: Proactive monitoring setup; tool selection; this skill = reactive takedown
  • branding: Brand asset protection; consistency
  • trust-badges: Official site verification signals
  • about-page: Official identity and domain declaration
  • homepage-generator: "Official website" placement
  • google-ads, paid-ads-strategy: Brand search ads for traffic recovery
  • schema-markup, title-tag: SEO for branded queries
Usage Guidance
This skill appears coherent for brand-impersonation response. Before installing: (1) understand it may read local project-context files (remove sensitive data from .claude/.cursor if you don’t want it used); (2) avoid uploading screenshots or customer data containing PII to public reporting forms—redact or get consent; (3) verify URLs and evidence before filing takedowns to avoid false reports; and (4) consult legal counsel for cease-and-desist/DMCA actions when unsure. No credentials or installs are requested, so the main risk is accidental disclosure of sensitive evidence when preparing reports.
Capability Analysis
Type: OpenClaw Skill Name: brand-protection Version: 1.0.1 The 'brand-protection' skill provides legitimate, non-executable instructions for an AI agent to assist users in identifying and reporting brand impersonation, phishing, and trademark infringement. It includes standard procedures for evidence collection and reporting to official channels like ICANN, Google Safe Browsing, and domain registrars (SKILL.md).
Capability Tags
cryptocan-make-purchases
Capability Assessment
Purpose & Capability
Name/description match the actions in SKILL.md: discovery, evidence collection, reporting to registrars/hosts/search engines, and legal/remediation guidance. The skill does not request unrelated credentials, binaries, or install steps.
Instruction Scope
Instructions are focused on collecting URLs, screenshots, WHOIS/hosting data and submitting reports to the listed abuse/reporting endpoints — all appropriate. The SKILL.md also instructs the agent to read local project context files (.claude/project-context.md or .cursor/project-context.md) for brand info; this is reasonable but the package metadata did not declare those config paths as required, so callers should be aware the skill may read those files if present.
Install Mechanism
Instruction-only skill with no install spec and no code files — minimal risk from installation or remote downloads.
Credentials
No environment variables, credentials, or config paths are required. All external interactions are to public reporting tools and lookup services appropriate to the task.
Persistence & Privilege
always is false and there is no behavior that modifies other skills or requests persistent agent-wide privileges.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install brand-protection
  3. After installation, invoke the skill by name or use /brand-protection
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
Automated batch sync
Metadata
Slug brand-protection
Version 1.0.1
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is brand-protection?

When the user faces brand impersonation, fake websites, phishing sites, or trademark infringement. Also use when the user mentions "fake site," "impersonatio... It is an AI Agent Skill for Claude Code / OpenClaw, with 95 downloads so far.

How do I install brand-protection?

Run "/install brand-protection" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is brand-protection free?

Yes, brand-protection is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does brand-protection support?

brand-protection is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created brand-protection?

It is built and maintained by Kostja Zhang (@kostja94); the current version is v1.0.1.

💬 Comments