Attacker uses the obtained credential, token, or session to log in. May test weak MFA factors (SMS, email) and swap them on the victim account to establish persistence.
Attacker profiles the tenant: queries /limits/ to learn API thresholds, lists all objects via /sobjects, then counts rows in sensitive tables (Account, Contact, User, Case) to scope the exfiltration.
Attacker pulls data using REST queries, Bulk API jobs, report exports, or file downloads — often staying within discovered API limits to avoid detection.
Attacker threatens to publish or sell stolen customer records, deal data, and PII unless a ransom is paid. Speed of detection between steps 2 and 3 is the primary window to contain the incident.