Skip to main content

November 13, 2026 security incident

Last updated: November 17, 2026

On November 13, 2026, Assembled had a security incident involving the database that stores the credentials used to connect to third-party integrations. This page answers common questions, including what to do if your account is affected. Our team is here to help with any additional questions or with re-authenticating your integrations. Reply to any of our communications about the incident, or contact our support team.

About the incident

Is the incident contained? Is it safe to reconnect?

Yes. Our engineering and security teams have confirmed it’s safe to reconnect.

How do you know new credentials won’t be compromised the same way?

We cut off the attackers’ access before issuing new credentials, and we’re continuing to monitor our systems closely.

When did the unauthorized access begin, and how long did it last?

Unauthorized activity took place between 06:54 and 10:20 GMT on November 13. The attackers have been removed, and the access path they used has been secured.

What was accessed? Was our data accessed?

The attackers accessed the database that stores integration credentials. These are the API keys, tokens and passwords Assembled uses to connect to your third-party systems, such as the integration between your contact center and Assembled. We’re treating all of those credentials as compromised. Separately, the attackers accessed conversations from Assembled’s own support account, including names, email addresses and messages exchanged with our team. We’re reviewing those conversations and will contact affected customers directly. The root cause analysis will cover the full scope of what was accessed.

Is there evidence our integration credentials were used?

We’re still reviewing whether any credentials were used. As a precaution, we’re treating all stored integration credentials as compromised, which is why we revoked what we could and are asking you to replace the rest. We’re also working with our integration partners to review their access logs. The root cause analysis will explain how we reviewed credential activity.

When will you share the root cause analysis?

We’ll share root cause analysis by Friday, November 20th at the latest. It will cover what was accessed, how we reviewed credential activity, and the corrective actions we’re taking.

What did Assembled revoke, and what does revoking mean?

Revoking a credential ends it in the system it belongs to, so it stops working for anyone who has it, including the attackers. It also disconnects that integration from Assembled until you reconnect it.

We revoked these integrations:

  • Zendesk
  • Salesforce, including sandboxes
  • Google Drive
  • Google Calendar
  • Slack
  • Zoom Contact Center
  • Intercom
  • Notion
  • Five9
  • The keys used for authenticated chat (JWT)

Reconnect these in Configure > Third-party integrations. Authenticated chat works differently, so follow its guide below. For Google Calendar, we'll contact you when it's time to reconnect. If that system’s admin settings still show an active Assembled connection, revoke it there before reconnecting.

What actions do I need to take? 

Reconnect with new credentials every other integration connected to Assembled, including Okta, Workday, and AI agent tools and connectors. We can’t revoke these from our side. For each one, create a new API key or password in that system, enter it in Assembled, then revoke the old one. Pausing or disabling an integration in Assembled doesn’t make the old credential stop working. Only revoking it in that system does. Note when you did, so you can scope your log review.

Which integrations on our account were affected?

Treat every integration connected to Assembled as affected. Reconnect the integrations we revoked, listed above, and replace the credentials for every other integration, including AI agent tools and connectors.

Do we need to rotate our Assembled API keys?

No. API keys your team created in Assembled to call our API are stored separately and don’t need to change. Credentials you saved in Assembled to connect to other systems are different. For each one, create a new API key or token in that system, replace the old one in Configure > Third-party integrations (or Configure > Tools and connectors for AI agent tools), then revoke the old key in that system.

Does the Assembled Chrome extension need to be reset?

No. The extension uses Assembled sign-in and we signed out every session as part of our response. If agents see the extension signed out or not loading data, they just need to sign in again.

 

Get help from our team

Can you share indicators of compromise or logs for our account?

Yes. We observed the attackers using two proxy IP addresses, 154.7.176.243 and 166.0.25.73, and testing an outbound connection to 172.236.83.240. User agents seen in attacker traffic include curl/7.88.1, curl/8, python-requests/2.34.2, Python-urllib/3.12, a bare Mozilla/5.0, and browser-style strings claiming Chrome 120, 122, 126 or 131 on Windows or Linux. The IP addresses are the more reliable indicator. For a review of activity on your account, contact our support team.

Can we meet with your security team?

Yes. Reply to any of our communications about the incident, or contact our support team. Include who from your team should attend and a few times that work, with your time zone, and we’ll schedule time with our engineering and security teams.

 

Reconnect integrations and replace credentials

Step-by-step guides for each integration are below. Start with the integrations we revoked, then replace the credentials for the rest. If your integration isn’t listed, follow the steps in What do we need to revoke on our side? above, or contact our support team.

Still have questions?