Hijack Defender
Detect, document, and remove unauthorized third-party sellers hijacking your Amazon listings or ecommerce product pages — with step-by-step enforcement workf...
Rank
62
Safety
84
Downloads
993
Updated
Oct 11, 2026
Version
1.1.0
Source
CLAWHUB
About
What it does, and when to use it.
Capability contract not published. No trust telemetry is available yet. 993 downloads reported by the source. Last updated 10/11/2026.
Avoid when
- Contract metadata is missing or unavailable for deterministic execution.
Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing
Public facts
Every fact links back to the source it came from.
- Vendor
- Clawhubvendor · observed Oct 11, 2026
- Protocol compatibility
- OpenClawcompatibility · observed Oct 11, 2026
- Adoption signal
- 993 downloadsadoption · observed Oct 11, 2026
- Latest release
- 1.1.0release · observed Jun 6, 2026
- Handshake status
- UNKNOWNsecurity
What changed
Newest first. Only changes that point at a source are listed.
Release 1.1.0release
No changes detected in version 1.0.2. - No updates have been made to the skill files. - All functionality and documentation remain the same as the previous version.
Observed Jun 6, 2026 · source
Install and run
Setup complexity: low.
clawhub skill install s17974h9acjg4h7h5djv1hg51d83hcca:hijack-defender- Install using `clawhub skill install s17974h9acjg4h7h5djv1hg51d83hcca:hijack-defender` in an isolated environment before connecting it to live workloads.
- No published capability contract is available yet, so validate auth and request/response behavior manually.
- Review the upstream CLAWHUB listing at https://clawhub.ai/leooooooow/hijack-defender before using production credentials.
Contract: missing
curl -s "https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-hijack-defender/snapshot"
Run-check
$0.02 USD1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.
Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.
Documentation
CLAWHUB
76,974 characters of source documentation, loaded on request.
Extracted files
5 files captured from the source.
SKILL.md
--- name: Hijack Defender description: Detect, document, and remove unauthorized third-party sellers hijacking your Amazon listings or ecommerce product pages — with step-by-step enforcement workflows for brand registry, cease-and-desist, and test buy procedures. --- # Hijack Defender Listing hijacking happens when an unauthorized seller attaches to your Amazon ASIN (or copies your product page on other marketplaces) and sells counterfeit, unauthorized, or gray-market goods under your brand name. It destroys customer trust, tanks your reviews, and can get your listing suppressed when Amazon receives complaints about products you didn't sell. This skill walks you through detecting hijackers, documenting the violation, submitting enforcement actions, and preventing future attacks. ## Quick Reference | Decision | Strong | Acceptable | Weak | |----------|--------|------------|------| | Detection method | Automated monitoring + daily alerts | Weekly manual checks | Reactive (noticing after damage is done) | | Evidence standard | Test buy + photos + invoices vs. yours | Photos only | Screenshots only | | Enforcement route | Amazon Brand Registry IP report | Case to Seller Support | Public seller feedback only | | Cease-and-desist | Attorney-reviewed template | DIY template | Verbal warning only | | Time to action | Within 24h of detection | 2–3 days | Week+ | | Prevention | Transparency program + brand registry | Brand registry only | No proactive measures | ## Solves 1. **Lost Buy Box** — Hijackers who undercut your price steal the Buy Box, diverting sales from your account to theirs. 2. **Review bombing** — Counterfeit products generate bad reviews on your ASIN that damage your conversion rate and BSR. 3. **Account suspension risk** — If Amazon receives too many A-to-Z claims about products "from your listing" that you didn't sell, your account can be suspended. 4. **Brand reputation damage** — Customers who receive counterfeit or sub-standard goods associate the poor experience with your brand. 5. **Price erosion** — Hijackers selling unauthorized inventory (often gray-market or end-of-life units) at deep discounts undermine your MAP pricing and devalue the brand. 6. **Slow enforcement loops** — Without documented evidence, enforcement cases get rejected or delayed. This skill builds an evidence package that gets cases resolved. 7. **Recurrence** — Without prevention systems (Transparency, brand gating), the same hijackers return after removal. This skill closes that loop. ## Workflow ### Step 1 — Set Up Monitoring Before a hijacker appears, set up automated detection: - **Amazon Brand Registry**: Use the Brand Dashboard to monitor your ASINs for new sellers. - **Seller monitoring tools**: Bindwise, Helium 10 Alerts, or SellerApp send alerts when a new seller appears on your listing. - **Manual check** (if no tools): Search your product on Amazon → click the "New & Used" offers → record current seller count and seller names. Set a monitorin
_meta.json
{
"ownerId": "kn70fv0ehp50emedet9tx3fekd82pw3b",
"slug": "hijack-defender",
"version": "1.1.0",
"publishedAt": 1780757057046
}cease-and-desist-template.md
# Cease-and-Desist Letter Templates ## Template A — Amazon Buyer-Seller Messaging (Counterfeit) **Send via:** Amazon Buyer-Seller Messages (go to seller's storefront → "Ask a question") --- Subject: Notice of Intellectual Property Infringement — Immediate Action Required Dear [Seller Name / Amazon Store Name], It has come to our attention that your Amazon seller account ([Seller ID]) is currently offering products on ASIN [ASIN] under the brand name [Your Brand Name] without authorization from [Your Company Name]. We are the owner of the registered trademark [TRADEMARK NAME], Registration No. [TM NUMBER], registered with the United States Patent and Trademark Office (USPTO). Your listing and/or products constitute: - Trademark infringement (use of our registered mark without authorization) - Unfair competition - [If applicable: Counterfeiting of our product and/or packaging] We have documented evidence of this infringement, including a test purchase conducted on [DATE], which confirmed the product sold under our brand name does not meet our authenticity standards. **We demand that you:** 1. Immediately remove your offer from ASIN [ASIN] and all related listings 2. Cease all sales of [BRAND NAME] products not purchased from [Your Company Name] or our authorized distributors 3. Provide written confirmation of compliance within 48 hours of this notice Failure to comply will result in formal trademark infringement claims filed with Amazon Brand Registry, as well as potential legal action including claims for actual damages, statutory damages of up to $2,000,000 per counterfeit mark under 15 U.S.C. § 1117, attorney's fees, and injunctive relief. This letter is not a complete statement of all rights or claims we may have, all of which are expressly reserved. Sincerely, [Your Name] [Title] [Company Name] [Contact Email] [Date] --- ## Template B — Amazon Messaging (Unauthorized Reseller / MAP Violation) Subject: Unauthorized Resale of [Brand Name] Products Dear [Seller Name], We have identified that your Amazon seller account is currently listing [Brand Name] products on ASIN [ASIN] at a price of $[PRICE], which is below our Minimum Advertised Price (MAP) of $[MAP PRICE] and/or without authorization to resell [Brand Name] products. [Brand Name] products are sold exclusively through our authorized retail partners. Your account does not appear on our list of authorized resellers. We request that you: 1. Immediately remove your offer from ASIN [ASIN] 2. Provide information about the source of your [Brand Name] inventory (invoice or purchase records) We are actively investigating the source of unauthorized [Brand Name] inventory in the market and will take appropriate steps to address supply chain violations. Your cooperation in identifying your source will be taken into account. Please respond within 48 hours. Sincerely, [Your Name] [Company Name] [Contact Email] [Date] --- ## Template C — Formal Legal Letter (Attorney-Ready Templ
checklist.md
# Hijack Defender — Enforcement Readiness Checklist Use this checklist before submitting any enforcement action. Incomplete evidence packages lead to rejected cases and allow the hijacker to continue operating. --- ## 1. Detection & Classification (5 items) - [ ] Hijacker identified with full seller name and seller ID captured - [ ] Violation type classified: Counterfeit / Unauthorized Reseller / Listing Copy / ASIN Piggyback - [ ] Hijacker's price vs. your price documented - [ ] Hijacker's seller account age and feedback rating noted - [ ] Detection date logged (for measuring time-to-resolution later) ## 2. Evidence — Listing Documentation (6 items) - [ ] Screenshot of hijacker's offer page (seller name, price, "Sold by" field visible) - [ ] Screenshot of your listing showing you as brand owner - [ ] Screenshot of "All Offers" display showing the specific hijacker offer - [ ] Hijacker's seller profile and feedback page captured - [ ] Date/timestamp visible in all screenshots - [ ] All screenshots labeled with ASIN, seller name, and date ## 3. Evidence — Brand Documentation (4 items) - [ ] Trademark registration number confirmed (USPTO TESS or equivalent) - [ ] Brand Registry enrollment confirmation on hand - [ ] Manufacturer invoice or purchase order confirming you as authorized seller - [ ] Authorized reseller list reviewed (is this seller on it? If yes, investigate MAP/contract violation separately) ## 4. Test Buy (for Counterfeit Cases) (7 items) - [ ] Test buy placed from a separate non-brand Amazon account - [ ] Order shipped to a neutral address (not brand business address) - [ ] Order ID documented - [ ] Package exterior photographed upon arrival - [ ] Side-by-side product comparison photos taken (authentic vs. received) - [ ] Packaging, inserts, and all materials preserved - [ ] Comparison photos clearly labeled: "authentic" vs. "hijacker" ## 5. Amazon Brand Registry Report (6 items) - [ ] Report submitted at brand.amazon.com → Report a Violation - [ ] Correct violation type selected (Counterfeit vs. Trademark) - [ ] ASIN and infringing seller URL provided - [ ] Trademark registration number included - [ ] Evidence photos attached (4–8 photos, clearly labeled) - [ ] Case reference number saved ## 6. Cease-and-Desist (4 items) - [ ] C&D message sent via Amazon Buyer-Seller Messaging to hijacker - [ ] Template customized with ASIN, trademark number, and specific violation details - [ ] 48-hour deadline stated in the message - [ ] Copy of sent message saved (screenshot or download) ## 7. Post-Resolution (6 items) - [ ] Hijacker's offer confirmed removed from listing - [ ] Reviews posted during hijack period reviewed for counterfeit complaints - [ ] Review removal requests filed for reviews about products seller didn't ship - [ ] Monitoring continued for 30 days post-removal (hijacker may return) - [ ] Estimated revenue lost during hijack period calculated - [ ] Incident logged in tracker with resolution date and method ## 8. Preve
evidence-collection-guide.md
# Evidence Collection Guide — Listing Hijack Cases ## Why Evidence Quality Determines Enforcement Speed Amazon resolves IP complaints on a tiered basis: - **Tier 1 (resolved in 1–3 days):** Trademark + test buy + photos showing clear counterfeiting - **Tier 2 (resolved in 3–7 days):** Trademark + screenshots showing unauthorized brand use - **Tier 3 (resolved in 7–30 days or rejected):** Screenshots only, no trademark, vague description Build Tier 1 evidence packages for every counterfeit case. --- ## Test Buy Protocol ### Before the Purchase 1. Create a dedicated "test buy" Amazon account separate from your brand account and any personal accounts. Use a neutral email address. 2. Use a shipping address that is not your business address (team member's home, P.O. Box, or package forwarding service). 3. Screenshot the listing before purchasing: show seller name, price, "Sold by" field, all listing images, and the date in the URL bar. 4. Note the specific offer you're buying (if multiple sellers exist, select the hijacker's offer explicitly). ### During the Order - Screenshot the checkout screen showing: seller name, price, and estimated delivery. - Note the order ID (format: 114-XXXXXXX-XXXXXXX). - Screenshot the order confirmation email. ### Upon Delivery Document the following the moment the package arrives — do not open fully until you're ready to photograph: **Package exterior:** - Photo of the package as received (all sides) - Photo showing return address label (seller's ship-from location) - Photo showing your order confirmation number on the packing slip **Product comparison photos (authentic vs. hijacker):** - Side-by-side packaging (front, back, sides) - Logo comparison (color accuracy, font, placement) - Barcode / UPC comparison (they often match but product inside differs) - Any authentication features: holographic stickers, serial numbers, QR codes - Inner packaging: foam, inserts, accessories, documentation - Product itself: material quality, construction, color accuracy - Any authenticity cards or certificates (present in authentic, absent or different in counterfeit) **Product testing (if safe and applicable):** - Weight comparison (counterfeits are often lighter) - Performance test documentation (e.g., battery life, output quality) - Ingredient or material discrepancy (for consumables or skincare) ### What to Preserve - The entire package, product, and all materials in the original received state - Digital photos organized by category (see above) - Order confirmation email as PDF - Tracking information from delivery *Do NOT dispose of any test buy materials until the enforcement case is fully resolved and any legal threats have passed.* --- ## Screenshot Documentation Checklist For every hijack incident, capture and label the following screenshots: ### Listing Screenshots - [ ] Full listing page showing: title, brand, images, price, "Sold by [Hijacker Name]" field - [ ] "All Offers" display showing the hijacker's off
AionUi
Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!
activepieces
AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
cherry-studio
AI productivity studio with smart chat, autonomous agents, and 300+ assistants.
CopilotKit
The Frontend for Agents & Generative UI. React + Angular
Machine-readable data
The same record, as JSON, for agents and crawlers.
- Card JSON
- Facts JSON
- Snapshot JSON
- Contract JSON
- Trust JSON
- Changes JSON
- Warnings JSON
- Seen by JSON
- Disagreements JSON
- Proof JSON
{
"facts": [
{
"factKey": "vendor",
"category": "vendor",
"label": "Vendor",
"value": "Clawhub",
"href": "https://clawhub.ai/leooooooow/skills/hijack-defender",
"sourceUrl": "https://clawhub.ai/leooooooow/skills/hijack-defender",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-11T21:02:02.665Z",
"isPublic": true
},
{
"factKey": "protocols",
"category": "compatibility",
"label": "Protocol compatibility",
"value": "OpenClaw",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-hijack-defender/contract",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-hijack-defender/contract",
"sourceType": "contract",
"confidence": "medium",
"observedAt": "2026-10-11T21:02:02.665Z",
"isPublic": true
},
{
"factKey": "traction",
"category": "adoption",
"label": "Adoption signal",
"value": "993 downloads",
"href": "https://clawhub.ai/leooooooow/hijack-defender",
"sourceUrl": "https://clawhub.ai/leooooooow/hijack-defender",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-11T21:02:02.665Z",
"isPublic": true
},
{
"factKey": "latest_release",
"category": "release",
"label": "Latest release",
"value": "1.1.0",
"href": "https://clawhub.ai/leooooooow/hijack-defender",
"sourceUrl": "https://clawhub.ai/leooooooow/hijack-defender",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-06-06T14:44:17.046Z",
"isPublic": true
},
{
"factKey": "handshake_status",
"category": "security",
"label": "Handshake status",
"value": "UNKNOWN",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-hijack-defender/trust",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-leooooooow-hijack-defender/trust",
"sourceType": "trust",
"confidence": "medium",
"observedAt": null,
"isPublic": true
}
],
"events": [
{
"eventType": "release",
"title": "Release 1.1.0",
"description": "No changes detected in version 1.0.2. - No updates have been made to the skill files. - All functionality and documentation remain the same as the previous version.",
"href": "https://clawhub.ai/leooooooow/hijack-defender",
"sourceUrl": "https://clawhub.ai/leooooooow/hijack-defender",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-06-06T14:44:17.046Z",
"isPublic": true
}
]
}Record generated Oct 13, 2026.
For crawlers
This page is free to read. The run-check above is the only paid part, and it answers HTTP 402 until it is paid. Everything else here is public.
- One record, as JSON: card, facts, snapshot, contract, trust, changes, warnings, seen by, disagreements, proof.
- Every agent, one feed: /.well-known/ai-catalog.json
- What this site sells, and the price: /.well-known/x402
- Paid run-check: /api/v1/agents/clawhub-leooooooow-hijack-defender/run-check
