> For the complete documentation index, see [llms.txt](https://support.backpack.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.backpack.exchange/exchange/security/i-suspect-unauthorized-access-to-my-account.md).

# I Suspect Unauthorized Access to My Account

### What to Do

1. **Change Your Password Immediately**

   * Log in and go to **Settings**.
   * Update your password with a strong, unique combination.
   * Visit [Backpack Exchange](https://backpack.exchange/settings/security).

   <figure><img src="https://1790800155-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3kiM6CAFBZoTCJcZ8X7k%2Fuploads%2FwokQl4wkzEVtegflIRRQ%2Fimage.png?alt=media&#x26;token=66100216-5bc8-42bb-81be-ca3cebe1eeb4" alt=""><figcaption></figcaption></figure>
2. **Enable Two-Factor Authentication (2FA)**
   * If not active, go to **Security Settings**.
   * Set up 2FA using a reliable app like Google Authenticator.
3. **Check Your Connected Accounts**
   * Go to **Settings** > **Security** > **Connected accounts**.
   * Disconnect any Google or Apple account you do not recognize. See [Connect or Disconnect Google or Apple](/exchange/security/google-and-apple-login/connect-or-disconnect-google-or-apple.md).
4. **Review Account Activity**
   * Check your transaction history for unfamiliar actions or transactions.
   * Contact us at **<support@backpack.exchange>** with details of your concerns.
   * Include any unusual activity you’ve noticed.

***

### Recognize and Avoid Phishing Attempts

To safeguard your Backpack Exchange account, it’s crucial to recognize and prevent phishing attempts. Follow these steps:

1. **Verify the URL**
   * Always ensure you’re accessing the official site: [https://backpack.exchange](https://backpack.exchange/).
   * Double-check the URL before entering any credentials.
   * *Note:* [*Official links to all Backpack Exchange and Backpack Wallet channels are located here.*](https://backpack.app/)
2. **Beware of Unsolicited Communications**
   * Be cautious with suspicious emails or messages claiming to be from Backpack Exchange.
   * We will **never** ask for your password or 2FA codes.
   * If anyone asks for them, they are a scammer.
3. **Examine Email Senders**
   * Double-check the sender’s email address.
   * Phishers may use addresses that look similar but with small alterations.
4. **Avoid Clicking on Suspicious Links**
   * Do not click on links or download attachments from unknown sources.
   * Hover over links to preview the destination URL before clicking.
5. **Report Suspicious Activity**
   * If you encounter anything suspicious related to Backpack Exchange, contact **<support@backpack.exchange>** immediately.

***

#### 🔒 Reminder

Your online safety is vital. By staying informed and cautious, you can protect your account and assets from potential threats.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.backpack.exchange/exchange/security/i-suspect-unauthorized-access-to-my-account.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
