Anonymized incident response | Healthcare
A trusted sender, a fake sign-in and a mailbox used to send phishing
A healthcare practice reported that a mailbox had been misused after a staff member opened a document-sharing lure from a known vendor. Evidence showed that the attacker passed the account’s existing two-step sign-in process, exported contacts, sent more phishing email and hid mailbox activity. The practice’s password change stopped the observed sign-ins; ACS then reviewed the cloud evidence and helped close additional access paths.
- Google Workspace
- Trusted-sender phishing
- Session and browser review
- Client identifiers withheld
This account is based on a confidential incident report supplied for publication in anonymized form. Names, addresses, domains, exact dates and operational identifiers are deliberately omitted. It describes an incident with open follow-up work, not a completed recovery or a guarantee for another organization.
Telltale signs
The warnings were technical as well as visual
A familiar sender and a successful MFA challenge did not make the activity safe. Several small signals formed a coherent incident when reviewed together.
A real vendor mailbox sent the lure
The message passed normal email authentication checks because it came from a real account. That is a reason to inspect the destination and request context, not proof that a link is safe.
The sign-in followed the document click
Cloud records connected the lure, an unfamiliar sign-in source and the subsequent account activity. The evidence was consistent with credentials and a one-time code being relayed in real time.
The mailbox suddenly sent a phishing wave
Unexpected outbound messages, contacts reporting odd email and replies about a document the user did not send were practical signs of compromise.
Evidence was deliberately hidden
Sent items, bounce notices and replies were moved or deleted. A block affecting bounce notifications also needed review. Browser synchronization and an unfamiliar extension entry expanded the scope beyond the password alone.
What helped
Contain access, preserve evidence and close the remaining paths
01
The user changed the password and warned contacts
The password change ended the attacker’s observed cloud sessions. The practice also removed old application connections and warned recipients rather than hiding the event.
02
ACS reconstructed the account activity
The team reviewed available sign-in, Gmail, application-authorization, browser-sync, contacts, administration and Drive records. This separated observed actions from things the logs could not establish.
03
Sessions and browser connections were revoked
The response included signing the user out, resetting sign-in cookies and revoking the browser connection associated with the risk. This went beyond changing the password again.
04
Mail and browser protections were tightened
Approved changes blocked the phishing destination, restricted risky mailbox-copy routes and unapproved applications, improved administrative alerts and constrained browser synchronization and extensions.
05
The evidence was retained for responsible follow-up
Relevant logs were preserved for the practice and its advisers. The response did not claim that exposed information could be recalled or that deletion could be undone.
Evidence and boundaries
What the review established—and what it did not
| Area | Evidence-supported finding | Responsible next step |
|---|---|---|
| Account access | The observed attacker sign-ins ended after the password change; later attempts did not succeed in the reviewed records. | Continue monitoring and use stronger sign-in controls suited to the account. |
| Mailbox behavior | Records showed outbound phishing, contact export, message access and concealment activity. | Review residual blocks, rules and access; involve the appropriate privacy, insurance and legal contacts. |
| Browser and endpoints | Browser-sync and extension evidence expanded the scope, but the computers had not been examined. | Inspect the affected devices and remove unauthorized browser artifacts using an authorized process. |
| Other cloud data | The reviewed records did not show Drive activity or a bulk mailbox export. | Record that as a bounded finding, not proof that no information was exposed elsewhere. |
The practice and its counsel remain responsible for breach determinations and notifications. Technical logs support those decisions; they do not replace legal advice or the organization’s policies.
Reduce the chance of a repeat
Turn the incident into an operating routine
The report identified practical improvements: stronger and consistently enforced authentication, controlled administrator recovery, application-approval boundaries, browser and device visibility, current account inventories, and alerts that reach a responsible reviewer.
The important distinction is ownership. A technical control without someone reviewing its alerts can leave an incident hidden. ACS Cyber can help an organization build that review path through managed detection and response, while Atlantic Computer Systems, our parent company, supports the wider managed IT environment.
Lessons another organization can use
- Verify unexpected document requests through a known channel
- Treat unfamiliar sessions and device registrations as investigation signals
- Review mailbox rules, blocks, delegation and connected applications
- Inspect affected endpoints instead of assuming a password reset is enough
- Preserve evidence before cleanup and involve the responsible advisers
Continue with the right resource
From an incident to a managed security baseline
What to do after a suspected compromise
Use a calm first-response sequence without destroying useful evidence.
Microsoft 365 payment-fraud investigation
See how hidden mailbox rules and automated reading supported fraud in a separate anonymized incident.
Security support for law firms
ACS Legal IT connects law-firm technology operations with ACS Cyber’s specialist security path. This incident was not a law-firm engagement.
Healthcare security coverage
Review managed security and incident support for healthcare organizations without assuming a compliance outcome.
A clear review when the signs do not add up
Do not stop at a password change without understanding the incident
If a mailbox is sending unexpected messages, sign-ins look unfamiliar or money or sensitive information may be involved, use your incident process and contact the appropriate bank, insurer and counsel. For active incident help from ACS Cyber, call our incident line at 1-650-300-7557 (after-hours emergency support is available). For a non-emergency coverage review, book a consultation.