Amazon Stealth Accounts: Proxy and Identity Setup That Actually Works

Amazon suspensions happen. Sometimes for legitimate policy violations, sometimes for ambiguous reasons, and sometimes for factors outside the seller’s control. When a suspension is final and appeals are exhausted, sellers face a choice: abandon the Amazon channel entirely or create a new account with infrastructure designed to avoid detection.

This guide covers the technical and operational requirements for creating and maintaining Amazon stealth accounts. The focus is on what actually works in practice — not theoretical advice, but the specific proxy, fingerprint, and identity isolation methods that sellers use to operate successfully long-term.

Why Sellers Create Stealth Accounts

Suspension Recovery

The most common reason is a suspended account with no viable appeal path. Amazon’s appeal process is opaque and inconsistent. Sellers with legitimate businesses sometimes exhaust all appeal options and face permanent removal from the platform. A stealth account is the path back.

Marketplace Expansion

Some sellers create accounts in multiple Amazon marketplaces (US, UK, Germany, Japan) and want operational isolation between them. While Amazon officially allows multi-marketplace selling under one account, some sellers prefer separate accounts per marketplace for risk isolation — a suspension in one marketplace does not propagate to others.

Product Category Testing

Sellers testing new, potentially risky product categories sometimes use a separate account to insulate their primary account from any policy issues during the testing phase.

Business Continuity

Established sellers with significant Amazon revenue sometimes maintain a dormant stealth account as a contingency plan. If the primary account faces issues, the stealth account can be activated to maintain revenue continuity.

Amazon’s Detection Signals

Amazon’s related account detection system (known internally as their “seller linkage” system) analyzes over a dozen signal categories. Understanding each one is necessary to build isolation that works.

IP Address History

Amazon maintains a comprehensive database of every IP address that has ever accessed Seller Central. When a new account is created or accessed from an IP that has historical association with a suspended account, the new account is flagged immediately.

This extends beyond exact IP matches. Amazon tracks:

IP ranges (/24 subnets) associated with suspended accounts
ISPs and carriers with history of suspended account access
VPN and proxy provider IP pools that have been used by suspended sellers

Browser Fingerprint

Amazon’s Seller Central pages collect detailed browser fingerprints:

Canvas rendering hash
WebGL renderer and vendor strings
Audio context fingerprint
Installed fonts
Screen resolution and color depth
Timezone and language settings
Hardware concurrency (CPU cores)
Device memory
Platform string

Amazon stores fingerprints historically. If a new account’s fingerprint matches or closely resembles a suspended account’s fingerprint, the link is established.

Cookie and Storage Data

Residual cookies, local storage entries, IndexedDB data, and service worker registrations from a suspended account’s browsing sessions can persist in a browser and leak into a new account’s sessions. Even a single shared cookie value creates a hard link.

Hardware Identifiers

On Windows, Amazon can access certain hardware identifiers through browser APIs and ActiveX controls. MAC addresses, hard drive serial numbers, and GPU identifiers have been reported as collection targets. On macOS and Linux, the exposure is more limited but not zero.

Payment Method Linking

Shared credit cards, bank accounts, payment processor accounts (PayPal, Payoneer), or even cards from the same issuer with sequential numbers can link accounts.

Business Information

Shared business names, EIN/tax IDs, addresses (including similar addresses within the same building), phone numbers, and email domains create links. Amazon cross-references business registry data in some cases.

Behavioral Patterns

Login timing, navigation patterns, typing speed, product selection approaches, pricing strategies, and seller support interaction styles all feed into behavioral models. These are harder to detect individually but contribute to a cumulative risk score.

Product and Catalog Overlap

Selling the same products, using the same product images, or copying listing content (titles, bullet points, descriptions) from a suspended account to a stealth account creates catalog-level linkage.

Shipping and Fulfillment

Shared FBA shipment origins, return addresses, carrier accounts, and warehouse locations link accounts. Amazon tracks where FBA inventory ships from and flags accounts with shared origin points.

Proxy Setup for Stealth Accounts

Choosing the Right Proxy Type

Mobile proxies are the only viable option for stealth accounts. Here is why each alternative fails:

Datacenter proxies: Immediately flagged by Amazon. No stealth account has ever survived long-term on datacenter IPs.

Residential proxies: Risky because many residential proxy pools have been used by other suspended sellers. Amazon has flagged significant portions of major residential proxy networks. There is a meaningful chance that your “clean” residential IP was previously used by another suspended seller.

VPN IPs: Amazon maintains blocklists of VPN provider IP ranges. Major VPNs are ineffective.

Mobile proxies: Fresh mobile IPs from real carriers rotate constantly through CGNAT, making historical contamination extremely unlikely. A mobile IP that is “yours” for today’s session was used by hundreds of legitimate Amazon shoppers yesterday.

Proxy Requirements for Stealth

Your mobile proxy must meet these criteria:

Clean history: The proxy provider’s IP pool should not be widely used by Amazon stealth sellers. If thousands of suspended sellers use the same provider, Amazon may flag the provider’s IP ranges. Choose a provider that is not the default recommendation in every Amazon seller forum.

Geographic match: The proxy must be from the same country as the Amazon marketplace. US mobile IP for Amazon.com. UK mobile IP for Amazon.co.uk. Mismatched geography is an instant flag.

Sticky sessions: You need the same IP for each Seller Central session. Rotating IPs during account management — appearing from one IP for login and a different IP five minutes later — triggers security verification.

Session duration: Sessions should last 30-60 minutes minimum. Short sessions followed by IP changes look like proxy rotation, not natural mobile usage.

Carrier diversity: If possible, use a major carrier (AT&T, T-Mobile, Verizon for US) rather than an MVNO. Major carrier IPs have the highest trust scores.

Proxy Operational Rules

One proxy per account, always. Never access the stealth account from any IP other than its dedicated proxy.
Never access the old account and the stealth account from the same proxy. Even sequentially. The IP link persists in Amazon’s records.
Never access the stealth account without the proxy. A single direct-IP access creates a link to your physical location and any accounts associated with it.
Use the proxy for all Amazon-related activities for that account: Seller Central, Seller Support chat/calls, advertising console, Brand Registry.

Browser Fingerprint Management

Anti-Detect Browser Setup

Use an anti-detect browser (Multilogin, GoLogin, or AdsPower) to create a browser profile for the stealth account.

Fingerprint generation: Generate a completely random fingerprint that does not resemble your suspended account’s fingerprint in any parameter. Pay special attention to:

Canvas hash: Must differ completely. The canvas hash is one of Amazon’s primary fingerprint matching criteria.
WebGL renderer: Choose a GPU renderer string that is different from your actual hardware and from any profile you have used before.
Audio context: Generate a unique audio fingerprint. Some anti-detect browsers handle this automatically; verify it.
Font list: Use a different set of fonts than your real system or previous profiles.
Screen resolution: Choose a common resolution that differs from your other profiles.
Timezone: Must match the proxy’s geographic location.
Language: Must match the marketplace’s primary language.

Profile consistency: Once configured, lock the fingerprint. Do not allow automatic updates or randomization between sessions. Amazon tracks fingerprint consistency — a device that changes its fingerprint every session is more suspicious than one with a stable fingerprint.

Operating System Isolation

For maximum safety, run the anti-detect browser on a different operating system than your primary machine:

Virtual machine: Run Windows in a VM on your Mac, or vice versa. This provides hardware-level isolation that prevents any system-level information leakage.
Separate physical machine: The most secure option. A dedicated laptop or desktop used exclusively for the stealth account.
Cloud desktop: Services like Shadow or Paperspace provide cloud-based desktops that are hardware-isolated from your local machine.

Testing Before First Login

Before logging into Amazon Seller Central with the stealth account:

Visit fingerprint testing sites (browserleaks.com, amiunique.org) from the stealth profile
Visit the same sites from your regular browser/profile
Compare every parameter — there should be zero overlap
Check for WebRTC leaks (should show only the proxy IP)
Verify timezone, language, and geolocation match the proxy

Identity Isolation Requirements

Business Registration

The stealth account needs a separate business entity:

Different business name
Different EIN/tax ID (for US) or equivalent in other countries
Different registered address (use a virtual office or different physical location)
Different business type if possible (sole proprietorship vs. LLC)

Contact Information

New email address from a different provider (if the old account used Gmail, use Outlook or a custom domain)
New phone number from a different carrier
New physical address for account correspondence

Payment Isolation

This is where many stealth accounts fail:

New bank account at a different bank than the suspended account
New credit/debit card from a different issuer
Different payment processor if applicable
No shared PayPal or Payoneer accounts between old and stealth accounts
Cards should not be from the same issuer in sequential number ranges

Product Catalog Separation

Do not sell the exact same products on the stealth account as the suspended account (at least initially)
Use original product photography
Write new listing content (titles, bullet points, descriptions) from scratch
Source from different suppliers if possible
Use different brand names

Account Warming Protocol

A stealth account must build organic-looking activity history before scaling to normal operations.

Phase 1: Initial Setup (Days 1-7)

Create the Amazon seller account through the stealth browser profile and proxy
Complete account setup (business information, bank account, tax interview)
Verify phone number and email
Do NOT list any products yet
Browse Seller Central naturally: review policies, explore the dashboard, read announcements

Phase 2: Soft Launch (Days 8-21)

List 5-10 products in a low-risk category
Set competitive but not aggressive prices
Enable FBA if applicable (ship from a different location than the suspended account)
Process initial orders carefully with excellent customer service
Respond to any Amazon messages or verification prompts immediately

Phase 3: Gradual Scaling (Days 22-60)

Increase product catalog to 20-50 items
Begin cautious advertising (low-budget campaigns)
Build organic sales velocity
Maintain excellent seller metrics
Introduce additional product categories gradually

Phase 4: Normal Operations (Day 61+)

Scale to target catalog size
Increase advertising budgets
Expand to additional categories
Maintain vigilant metric management

Rushing any phase is the most common cause of stealth account detection. Amazon’s systems are designed to catch accounts that ramp up too quickly.

Common Failures and How to Avoid Them

Failure 1: Residual Browser Data

Clearing browser data is not sufficient. Traces of previous sessions can persist in:

Service worker registrations
WebSQL databases
Cache API storage
Credential manager entries

Solution: Always use a fresh anti-detect browser profile created specifically for the stealth account. Never repurpose or modify an existing profile.

Failure 2: Network-Level Leaks

DNS requests, WebRTC connections, and system-level network activity can bypass the proxy and reveal your real IP.

Solution: Configure DNS to route through the proxy. Disable WebRTC or configure it to use the proxy IP. Consider running the stealth browser in a VM with network-level proxy enforcement (all traffic from the VM routes through the proxy).

Failure 3: Physical Address Proximity

Using an address in the same building, block, or even neighborhood as the suspended account raises flags. Amazon geocodes addresses and checks proximity.

Solution: Use a virtual office address in a different city. Many virtual office services provide a real street address with mail forwarding.

Failure 4: Behavioral Signature Replication

Accessing Seller Central at the same times, navigating the same pages in the same order, and making the same types of changes as the suspended account replicates a behavioral signature.

Solution: Consciously vary your workflow. Access at different times. Navigate differently. Change your operational patterns.

Failure 5: Shared Wi-Fi or Network

Accessing the stealth account and any other Amazon account (personal buyer account, other seller accounts) from the same Wi-Fi network or router creates a network-level link.

Solution: The stealth account should only be accessed through its dedicated proxy, from a device that does not connect to any network shared with other Amazon accounts.

Long-Term Maintenance

Stealth accounts require ongoing discipline:

Never mix environments. The stealth account’s browser profile and proxy are used exclusively for that account, permanently.
Monitor for verification requests. Respond to any Amazon verification prompts immediately and calmly.
Maintain excellent metrics. Stealth accounts under scrutiny receive more automated reviews. Perfect metrics reduce review frequency.
Stay current on Amazon’s detection. Amazon continuously improves their detection. What works today may need adjustment in six months.

For broader multi-account management strategies across platforms, see our multi-account proxies guide. For Amazon-specific account management (not stealth-specific), our Amazon seller proxy guide covers the fundamentals.

For a complete overview of proxy usage across e-commerce platforms, visit our e-commerce proxy hub.

Need clean mobile IPs for a fresh start? Explore DataResearchTools’ mobile proxy plans — carrier-grade IPs with no prior association to flagged accounts.