Amazon Seller Account Hacked Recovery Playbook
This article is for informational purposes and not to be construed as legal advice. No attorney-client relationship exists based on the review of this article, and none of the information in this article is legal advice.
You open Seller Central to check a missing payout. You find a bank account you don’t recognize. There are listings you never created. Buyers are asking about orders you can’t identify. That is not a routine glitch. Treat it as a suspected takeover until you can rule it out.
You now have three problems. One is access. One is evidence. One is your account health. A new password fixes only the first.
Recognize the Breach and Prioritize
The signs usually show up in pieces. The payout account has unfamiliar digits. A new user appears in permissions. Prices drop on products nobody touched. Customers complain about items that never shipped. One sign alone may have another cause. Several unexplained changes together call for fast containment.
This has happened before. In 2017, Dow Jones reported that hackers used stolen email and password credentials to change bank deposit details on Amazon seller accounts, post fake listings, and take the proceeds. Some of those accounts were dormant. The lesson is simple. Attackers usually want the payout stream, a trusted storefront, or both.
Signals That Justify Immediate Action
Don’t wait for certainty if you see several of these signs.
- Changed payout or contact details: A bank account, email, or phone number nobody on your team approved.
- Unfamiliar users or permissions: A new user, a higher-level role, or an invitation you didn’t send.
- Catalog changes you can’t explain: New listings, edited condition notes, steep discounts, or products you don’t sell.
- Order and message anomalies: Refunds, cancellations, or complaints about orders you never fulfilled.
- Access alerts you didn’t trigger: Password reset notices or verification codes nobody asked for.
A single listing error may just be a catalog issue. A suspension notice with no unauthorized edits is usually an enforcement issue. When credentials, payments, users, and listings change together, treat it as a suspected compromise.
Practical rule: Contain first. Document right after. Dispute account consequences with evidence, not memory.
Your first goals are narrow. Stop further changes. Save what the account shows right now. Avoid bulk edits that erase the trail. Don’t open a new seller account to get around a lockout. That creates a separate policy problem. It also does nothing to recover the original account, its funds, or its history.
Contain Access and Payment Exposure
Use a device you control. Type the Seller Central address yourself or use a saved bookmark. Don’t use links, phone numbers, or QR codes from a suspicious message. If you see an unauthorized payout change or user, contain it now. Then capture the record.
The steps below put the most urgent fixes first.
Lock the Account and the Mailbox
- Change the Seller Central password: Use a unique password you don’t use anywhere else. If you’re locked out, contact Seller Support through a known Amazon address.
- Secure the email account: Give it a different unique password and turn on multifactor authentication. Check recovery addresses, forwarding rules, active sessions, and connected devices. A hacked mailbox can undo every other fix.
- Review two-step verification: Confirm that every method and phone number belongs to you. Remove anything you can’t explain.
- Audit users: Remove unfamiliar users. Cut back permissions that are broader than the work requires.
Amazon requires two-step verification to sign in to Seller Central. Amazon’s seller forum guidance lists an authenticator app, a text message, or a voice call as options. Each user sets up their own verification. An authenticator app on a device you physically hold is a sound choice. If an attacker changed your verification method or controls your phone number, treat that channel as part of the incident. Don’t rely on it to recover.
Stop the Money From Moving
Once access is stable, check deposit methods, charge methods, payout status, and recent account notices. If payout details changed, call the bank tied to the account. Ask what is pending, what has completed, and what monitoring or recall options exist. Save every alert, confirmation, and reference number.
Restoring the right bank account does not reverse a transfer that already left. Amazon controls the seller account and its payout settings. Your bank controls its own transfers. You will likely need both conversations, each with its own case number. That split also matters if orders created during the takeover lead to an Amazon chargeback dispute.
Know What Containment Doesn’t Fix
A password reset closes one door. It doesn’t restore altered listings. It doesn’t release held funds or remove fraudulent orders. It doesn’t clear account health defects. It also doesn’t prove the account is clean if a rogue user or changed recovery setting remains.
End containment with a check. Confirm that only approved users remain. Confirm that your verified bank account is showing. Confirm that contact details match your records. Watch for new changes after the reset. Then start documenting.
Build the Incident Evidence File
Memory fades fast. Amazon, a bank, an insurer, or the police may ask what changed, when you found it, and what proves it. Build one file, in time order, that answers those questions.
Start with what the account shows right now, before routine work overwrites it.
What to Capture
- Screenshots with context: Capture full pages that show the account, the changed field, and the date. Name files so a stranger can follow them later.
- Payout and order records: Download payout history, affected order IDs, refund records, and payment change notices.
- Access records: Save the user list, permission levels, login alerts, and verification changes.
- Catalog evidence: Record affected ASINs, listing edits, condition note changes, and prices.
- Messages and cases: Keep phishing emails, buyer complaints, bank alerts, and every Amazon case message.
Scale is real. In 2018, CRN reported, citing Bloomberg, that about 100 Amazon merchant accounts were compromised over roughly six months. Account details were changed so that loan funds or sales proceeds went to bank accounts the attackers controlled. That is why payout history and permission records belong in your file. They help show an unauthorized change rather than a normal business update.
Turn Files Into a Timeline
Create one log with a row for each change you found. Record when you found it and the time zone. Note the original value if you know it, the value you found, and the fix you made. Note who made the fix and which screenshot supports the row. Write unknown instead of guessing.
Keep facts apart from opinions. Write “unauthorized change” or “unknown actor” unless you have proof of who did it. That keeps your account credible if Amazon or a bank reviews it later.
Store a copy outside the hacked mailbox. Keep it off any shared drive the attacker may have reached. Before you share the file outside your business, mask full bank numbers, tax data, verification codes, and customer details you don’t need to share. A clear evidence file does not guarantee reinstatement or repayment. It does make every later conversation specific and consistent.
Recover the Amazon Seller Account
Report the incident to Amazon as unauthorized access, not as a vague account problem. A case that says “something is wrong with payments” tends to get a generic payment answer. A case that names unauthorized access, lists what changed, and attaches a timeline gives the reviewer a security incident to look at.
Use official Seller Central Help channels reached through a known Amazon address. Keep one main case if you can. Reference earlier case numbers in updates. Pick one person on your team to handle all contact with Amazon.
What Amazon Says to Check
Amazon’s Seller Central help page on keeping account information secure gives a short list. Change your Seller Central password, and contact Seller Support if you can’t sign in. Review listing and condition notes, storefront details, user permissions, payment information, and email preferences. Amazon notes that the email account tied to Seller Central may also be compromised, and suggests using a different password for it. Report phishing emails to [email protected]. Contact Seller Support to report the problem.
Your report to Amazon can follow the same list. State what you found in each area.
- Access and email preferences: Current sign-in status, changed email or phone settings, verification methods, and users you removed.
- Payment information: The deposit and charge methods you found, the details you restored, and payouts you believe were diverted.
- Storefront details: Any changed business name, address, tax, or contact information.
- Listings and condition notes: Affected ASINs, unauthorized offers or edits, and whether you paused or fixed them.
- Orders and customer impact: Fraudulent orders, refunds, cancellations, buyer messages, and related account health notices.
End with specific requests. Ask Amazon to confirm the correct account information. Ask it to look into the changes you found. Ask how affected payouts and orders will be handled. Ask what steps remain. Vague requests get vague replies.
Organize the Case Before You Submit
Prepare a short packet. Include your store name and marketplace, masked account numbers, the first sign and its time, a short timeline, the containment steps you finished, and labeled attachments.
Log every case number, document request, reply, and next step. If Amazon also restricts your selling privileges, that is a separate track. Use the same timeline, but don’t merge the two cases. Our guide to the Amazon suspension appeal and Plan of Action covers that track. The security case still needs to resolve the unauthorized access.
If Amazon Requests a Plan of Action
Keep it short and specific. Name the concern Amazon raised. Tie it to the documented unauthorized activity where the evidence supports that link. State the fix you completed and attach proof. Describe the safeguard that prevents a repeat. Don’t claim a root cause you haven’t confirmed. Don’t promise outcomes you can’t control.
A strong submission ties each problem to a documented change and a finished fix. “We were hacked” on its own carries far less weight.
Nobody can promise reinstatement or a timeline. Amazon decides. Track open items by owner and date. Keep watching for new changes. Don’t close the incident while an unexplained user, payout gap, policy notice, or support case is still open.
Coordinate Amazon and Financial Institutions
Sellers lose time when they ask one organization to fix another one’s problem. Amazon reviews account access, listings, orders, and account settings. Your bank reviews transfers on its own system. A card issuer handles card charges through its own dispute process. Run these as parallel tracks.
Write a separate, factual summary for each one. Include dates, amounts from your own records, masked account numbers, order or payout IDs, other case numbers, and the exact action you want. Keep the facts consistent. Tailor the request.
Who Can Address Which Loss
| Organization | Issues to Raise | Evidence to Provide |
|---|---|---|
| Amazon | Unauthorized access, users, listings, orders, payout settings, account health defects | Timeline, screenshots, affected ASINs and order IDs, containment steps, case numbers |
| Bank or payment processor | Diverted or pending transfers, exposed account details, monitoring or recall options | Bank alerts, payout records, dates and amounts, Amazon case number |
| Card issuer | Unauthorized card charges tied to the account or connected services | Statements, transaction IDs, dispute forms, proof the charge wasn’t authorized |
| FTC or local police | Misuse of personal identifying information | Reports where appropriate, saved messages, login alerts, payment change records |
The FTC’s Data Breach Response: A Guide for Business says to update the credentials of authorized users. It says not to destroy evidence. It also suggests talking with legal counsel. If employee or customer information was exposed, notice rules may apply. Those rules depend on the data and the states involved, so get advice on your own facts.
Questions That Get Useful Answers
Ask Amazon which payout records and change notices can support a bank inquiry. Ask the bank what it can confirm in writing about pending, completed, returned, or lost transfers. Ask each one what deadline applies, what form it needs, and whether one dispute affects another.
Customers need clear answers, not the full story. Handle refunds, cancellations, and messages through Amazon’s systems. Document each decision. Don’t accuse a named person without proof. Don’t promise customers a refund outcome that hasn’t been confirmed.
Results depend on the facts, the institutions, the payment method, and the rules that apply. Amazon may restore access while a bank declines a recall. Track each item separately so a win in one place doesn’t hide a loss somewhere else.
Sort Out the Losses
Recovery routes are not interchangeable. A payment dispute, an Amazon reimbursement request, an inventory claim, and an identity theft report go to different decision makers. Sort each loss first. Then choose the process. Using the wrong process can cost you a deadline in the right one.
Match the Loss to the Route
- Diverted payouts: Ask the bank whether a recall, return, or fraud investigation is available. Get deadlines in writing.
- Fraudulent card charges: Ask the issuer whether a dispute process applies to that charge. A bank transfer may not carry the same rights.
- Marketplace losses: Raise seller-charged refunds, fraudulent orders, fees, and account health defects with Amazon. Tie each one to order IDs and your timeline.
- Inventory: Document removals, stranded inventory, shipment changes, and fulfillment setting edits on their own. Restoring access doesn’t replace stock.
- Insurance: Read your actual policy and its notice rules. Coverage varies. Late notice can create its own problem.
An institution may confirm that a process exists and still deny the claim. Keep any denial and its stated reason. That reason helps you decide whether an appeal, complaint, or legal review makes sense.
Identity Theft Reporting
If your personal information was misused, the FTC’s IdentityTheft.gov recovery steps explain how to report it. You can report online or call 1-877-438-4338. IdentityTheft.gov then creates an Identity Theft Report and a recovery plan. You may also choose to file a report with your local police.
Bring your organized file. A short timeline, proof of identity, records of the unauthorized changes, and copies of Amazon and bank messages make the report easier to file and use.
When to Talk With a Lawyer
Some situations call for legal help. Losses may be large. Funds or inventory may stay held. A bank or insurer may deny a claim. Personal data may be exposed. Amazon’s position may leave a dispute you can’t resolve through Seller Support. A lawyer can review contracts, payment rules, insurance terms, and the options that fit your facts. A general guide can’t do that.
Don’t wait until evidence is gone. Keep devices, messages, logs, and account exports. Tell your team not to delete suspicious emails or overwrite listing files. Deadlines depend on the facts, and delay can narrow your options.
Prevent the Next Seller Account Takeover
Prevention is more than a longer password. Build a setup where one stolen password, one former contractor, or one forgotten account can’t redirect money or post listings in your name. Focus on the places attackers use: logins, email, verification, users, payments, and dormant accounts.
Start with this checklist once recovery is stable.
Access Controls That Hold Up
- Unique passwords: Use a password manager. Never reuse the Seller Central password for email, banking, advertising, or supplier sites.
- Verification on both doors: Protect Seller Central and its mailbox. Securing one and not the other is a common gap.
- Controlled recovery email: Limit who can use it. Review forwarding rules and recovery contacts. Don’t treat it as a shared inbox.
- Least-privilege users: Give staff and agencies only the permissions their work needs. Remove access the day a person or vendor leaves.
- Connected apps and brand roles: Review authorized apps, API connections, and Brand Registry roles on a schedule. Our Amazon Brand Registry guide covers related brand controls.
Payment Change Rules
Make a rule that nobody changes a payout account based on an email, chat, or prompt alone. Verify payment changes through a separate, known contact method. Require two authorized people to approve. Record the approval in your finance log. If your business is too small for two approvers, use a waiting period and a call to a known internal number first.
Treat any payout change you can’t trace to two known people and a written approval as unauthorized until proven otherwise.
Reconcile payouts against orders and bank deposits on a set schedule. A missing payout is a finance alert. Don’t wait another cycle to look into it. Send bank alerts to an address someone checks every day.
Dormant Accounts and a Practiced Response
An inactive seller account still has a storefront, a login, and a history. Protect it like an active one. Use the same passwords, verification, mailbox protection, and regular login checks. If you no longer need it, close it properly. An account nobody watches is the easiest one to misuse.
Keep an incident folder ready. Include contacts for your account admin, finance lead, bank, insurer, IT support, and lawyer. Add templates for the timeline, evidence log, Amazon case summary, and bank notice. Decide in advance who changes passwords after hours, who calls the bank, and who handles customers.
After recovery, keep watching login alerts, payout changes, user access, listings, orders, connected apps, and open Amazon cases. Close the incident only when every unexplained item has an owner and an answer.
LA Law Group, APLC works with Amazon sellers on account health, suspension, and appeal issues. To discuss your notice, visit our Amazon seller lawyer page or call (866) 625-2529. Our Chatsworth office is at 21540 Prairie St Unit A, Chatsworth, CA 91311.
This article is general information, not legal advice, and does not create an attorney-client relationship. Laws change and every situation is different. For advice about your specific matter, speak with a licensed attorney. Attorney Advertising.
Photo: Dan Nelson on Pexels (photo 4973899), Pexels License. Cropped and resized to 1600 by 900; a small logo inside the on-screen padlock was blurred; no other edits.
Frequently asked
What should I do first if my Amazon seller account is hacked?
Change your Seller Central password. If you are locked out, contact Seller Support. Then secure the email account tied to Seller Central with a new, different password. Amazon's help page on account security also says to review listings, storefront details, user permissions, payment information, and email preferences.
Does Amazon require two-step verification for Seller Central?
Yes. Amazon requires two-step verification to sign in to Seller Central. Amazon's seller forum guidance lists an authenticator app, a text message, or a voice call as verification options. Each user on the account sets up their own verification.
Can Amazon reverse a payout that went to a hacker's bank account?
Nobody can promise that. Amazon controls the seller account and its settings. Your bank controls its own transfers. Contact both, keep the case numbers separate, and get each answer in writing.
Should I report an Amazon seller account takeover to the FTC?
If your personal information was misused, the FTC's IdentityTheft.gov site lets you report it online or by phone at 1-877-438-4338. The site then creates an Identity Theft Report and a recovery plan. You may also choose to file a report with your local police.
Attorney Advertising. This article is general information, not legal advice, and does not create an attorney-client relationship. Prior results do not guarantee a similar outcome.