Shinyhunters on CuraSec

McKesson discloses breach; ShinyHunters claims 284M patient records

Sat, 29 Aug 2026 15:36:18 +0000

Engineer — Learn: Breach was via unauthorized access to third-party applications, not a patchable CVE; reinforces the need to audit and restrict third-party SaaS access, but no concrete engineering action is available from this disclosure alone.
SOC/IR — Learn: ShinyHunters attribution is a useful actor profile update, but no IOCs, TTPs, or detection-relevant technical detail are published yet; monitor for follow-on disclosures that include actionable indicators.
Leader — Act: McKesson is a major healthcare and pharma supply chain vendor — if your organization has a relationship with them, confirm exposure scope this week and request their incident attestation; 284 million claimed patient records puts this in HIPAA notification and board-visibility territory.

Thu, 27 Aug 2026 21:01:55 +0000

Engineer — Skip
SOC/IR — Learn: ShinyHunters continues active extortion operations; no IOCs or TTPs published from this incident to act on, but useful for tracking the group’s targeting patterns.
Leader — Act: If Carhartt is a vendor or employee-benefits partner, request their incident report and confirm scope of data shared; separately, brief leadership given the scale (12.9M accounts) in case customers or press ask.

Tue, 25 Aug 2026 11:39:54 +0000

Engineer — Learn: ShinyHunters used internal-impersonation social engineering to target a security vendor employee; no software vulnerability involved, but worth reviewing your own internal verification procedures for sensitive access requests from apparent colleagues.
SOC/IR — Learn: Confirms ShinyHunters is actively targeting security vendor employees via insider-impersonation lures; no IOCs or ATT&CK-mappable TTPs are published here, so no immediate detection work is actionable.
Leader — Plan: If ReliaQuest is in your vendor stack, formally confirm with them that no client data was at risk during this incident and request a written attestation; the failed outcome reduces urgency but does not eliminate the vendor-risk checkbox.

Sun, 26 Jul 2026 12:14:17 +0000

Engineer — Skip
SOC/IR — Learn: ShinyHunters-leaked emails are now being used as lures in sextortion campaigns; no novel TTPs or IOCs are provided, but awareness helps triage any related user-reported phishing tickets.
Leader — Learn: If your organization’s user emails were exposed in ShinyHunters breaches, employees may receive these extortion emails; brief HR and helpdesk on the campaign so they can field employee reports without escalating to a formal incident.

Tue, 14 Jul 2026 12:08:08 +0000

Engineer — Plan: No platform CVE to patch — the attack surface is over-trusted OAuth connections and third-party integrations. Audit all connected apps in your Salesforce org, revoke unused OAuth grants, and review third-party vendor permissions this quarter.
SOC/IR — Act: Microsoft has detailed three concrete attack paths from an active, year-long campaign — hunt for anomalous OAuth authorization events and unusual connected-app activity in Salesforce audit logs going back at least 12 months to check for prior compromise.
Leader — Act: ShinyHunters is an active data-extortion group and this campaign abuses third-party SaaS trust, not software flaws — confirm your organization’s Salesforce OAuth integrations are inventoried, brief leadership on third-party SaaS risk exposure, and ask your Salesforce-connected vendors for attestation of their OAuth hygiene.