Live threats
HighClaude Dispatch Flaw Enables Browser Extension RCE on Host OS BreachBrenner Base Tunnel SE Confirms Data Breach; Extortion Group Claims 812 GB Stolen Rule changeOPM proposes to modify OPM/Central-21 system of records and rename employee survey DeadlineEgyptian court fines and orders closure of independent outlet Mada Masr, sentencing editor Lina Attalah CriticalCritical OpenSSH Auth Bypass Flaw Lets Long Passwords Circumvent Authentication on Alpine Linux BreachDigiCert Migration Misconfiguration Exposes Customer Identity Documents FineCommission preliminarily finds TikTok’s ‘For You’ feed breaches DSA over harmful ‘rabbit hole’ effect CriticalPatched Zyxel GS1900 Switches Remain Exploitable (CVE‑2026‑107441)
Updated 06:24 UTC All intelligence →
BREACH WATCH BRIEF Critical 🎣 Breach

Fake Job Interview Social Engineering and Tampered Homebrew Tool Enable $6.43 B Theft from Binance

Binance reported that attackers used a fake recruitment interview and a compromised Homebrew installer to capture privileged credentials, resulting in a $6.43 billion theft. The breach highlights the importance of robust identity‑and‑access controls and verification of third‑party tooling for audit readiness.

SeverityCritical
Type🎣 Breach
ConfidenceHigh
ReportedNov 3, 2026
Financial Services & FinTech FIN_SERV Phishing Credential Compromise

What happened

Binance disclosed a multi‑stage campaign that began with attackers posing as recruiters and conducting fake interview calls with two senior engineers. During the interview, the engineers were instructed to download a tampered Homebrew package, which installed a back‑door on their workstations. The back‑door harvested privileged credentials and API keys, allowing the threat actors to move $6.43 billion from Binance’s hot wallets over several weeks before the breach was detected. Binance emphasized that the attack combined social engineering, supply‑chain manipulation, and credential abuse rather than a single phishing email.

Why it matters for trust and compliance

  • The incident demonstrates that without strong identity‑and‑access controls and rigorous verification of third‑party development tools, organizations cannot reliably demonstrate control assurance across frameworks such as NIST CSF or ISO 27001.
  • Provides evidence for privileged‑access monitoring controls required in audit frameworks.
  • Supports continuous‑evidence collection on third‑party tool integrity for supply‑chain risk assessments.

Who is affected

FIN_SERV

Recommended actions

  1. Enforce multi‑factor authentication and least‑privilege for all privileged accounts.
  2. Adopt signed‑binary verification and hash checks for all third‑party development tools.
  3. Run regular security‑awareness simulations that include recruitment‑scam scenarios.
  4. Implement continuous monitoring of privileged credential usage and anomalous API calls.

Regulations library

Every US state privacy law, on one map

24 states have a comprehensive privacy law in the library, alongside the EU, UK, US federal and global laws: 102 in all, each explained in plain words with its sources. Select a state to see what applies there.

  • In force
  • Coming into force
  • Sector laws
AK ME VT NH WA ID MT ND MN IL WI MI NY RI MA OR NV WY SD IA IN OH PA NJ CT CA UT CO NE MO KY WV VA MD DE AZ NM KS AR TN NC SC DC OK LA MS AL GA HI TX FL

Get the Breach Digest

The incidents that matter for your vendors and your data, analyzed for practitioners, in one email.