1-minute read
What a defender needs to know
Attackers breached Klue in June, stole customer OAuth tokens and used them to query Salesforce data directly. Huntress said the initial access came through a long-disused credential created for an abandoned prototype integration. The intruder then added code that collected tokens belonging to Klue customers.
Public notices from Huntress, HackerOne and OneTrust place the exposed information inside CRM and sales systems. The records included business contacts, account details, pricing and sales communications. The affected companies reported no access to their core products. Valid tokens let the API requests authenticate normally, so login-failure alerts would have missed the activity.
Inventory connected apps down to their live credentials. Record the owner, OAuth scopes, service account, refresh tokens, expected source networks and last legitimate use. During a vendor incident, preserve API logs before their retention windows close, then revoke affected app grants, sessions and refresh tokens. Rotate credentials shared with the vendor. Alert on unfamiliar source networks, user agents and sudden changes in object access or query volume.
Prototype and abandoned integrations belong in the same review. A project ending does not remove the access it created.
Inventory active grants, sessions and refresh tokens for every vendor integration. Revoke abandoned access and verify that retained credentials come only from approved networks and expected API behavior before restoring the connection.