Suspicious AI Account Activity: Unexpected Chats and Possible Account Compromise
An AI account may hold conversation history, uploaded files, connected applications, billing details, and access to workplace tools. Unexpected chats or unfamiliar activity can therefore signal more than a display error. They may indicate a stolen password, reused credentials, an exposed browser session, a shared device, a malicious extension, or unauthorized access through a connected service. Act promptly, but preserve enough information for the security team to investigate.
Warning signs
Possible indicators include chats you did not create, prompts in a language or style you do not use, renamed or deleted conversations, unfamiliar files, unexpected model usage, unknown devices or sessions, changed profile or recovery details, new connectors, surprising subscription or API charges, and security alerts you did not trigger. Also watch for MFA prompts, password reset messages, or login notifications when you were not signing in.
An AI assistant sending messages, opening resources, or taking actions you did not request is urgent. So is a coworker receiving strange content from your account. One odd chat may have an innocent explanation, such as a shared workstation, but it still deserves verification.
Safe steps
- Stop using the account for sensitive work. Do not continue chatting, upload files, or delete the suspicious conversations. If the service is taking actions, close the session and contact security.
- Use a known-safe device and official site. Navigate from a bookmark or type the provider's address yourself. Do not use a link from an alert email or text.
- Review security activity. Check recent logins, active sessions, connected apps, browser extensions, profile details, recovery methods, and billing history if these views are available. Capture only the minimum screenshots allowed by policy.
- Change the password. Create a long, unique password using the approved password manager. If that password was reused anywhere else, change those accounts too, beginning with email. Never place the new password in a ticket or chat.
- Sign out other sessions. Use the provider's option to log out all devices or revoke sessions. Remove unknown connected apps, API access, or extensions only after recording their names for the ticket.
- Enable or reset MFA. Choose an approved method and save recovery codes only in an approved secure location. Deny any MFA prompt you did not initiate.
- Check the device. Install approved updates and run the organization's security scan. If you suspect malware or a malicious extension, stop and ask security before making broad changes that could remove evidence.
- Notify affected people. If the account sent content or shared files, tell security which contacts or systems may be affected. Let the response team coordinate any wider warning.
What not to do
Do not delete unexpected chats, wipe the device, confront a suspected person, or repeatedly sign in from different devices. Do not use search ads to find support or pay anyone claiming they can recover the account. Never disclose passwords, MFA codes, recovery codes, API keys, secrets, customer data, health data, financial data, source code, contracts, or confidential documents in a support request. Do not copy private chat history into an unapproved tool.
When to escalate
Contact security immediately if the account performed actions, exposed workplace data, used a connector, generated charges, changed recovery details, or remains accessible to an unknown session. Escalate any unauthorized MFA approval, reused password, malware concern, or compromise of the email account tied to the AI service. If you cannot sign in, use the provider's official recovery process and notify security through a known channel.
What to include in the ticket
Include the account email or username, service name, first and last known normal use, time the suspicious activity appeared, and a description of unfamiliar chats, sessions, connectors, charges, or alerts. State whether the account is personal or organization-managed and which steps you completed. List affected devices and browsers. Include screenshots only if they do not expose protected content. Never include passwords, MFA or recovery codes, API keys, full payment details, confidential prompts, or uploaded files.