Sherlock

Account Compromise

Estimated loss

—

VERDICT —OUT OF SCOPE

Root cause is phishing — victims signed malicious transactions or approvals off-protocol. Contract logic was not the failure surface; user-side wallet hygiene was. Pre-deployment audit cannot catch this class.

▰ METHOD

PHISHING

Root cause

Root-cause analysis not yet published. The incident description below contains all currently available signal — review the attack transaction directly for definitive forensics.

Forensic narrative

The Twitter account of the security company @sherlockdefi was hacked, with the attackers using the account to post a tweet containing phishing links. Attack method (per SlowMist): Account Compromise. Reported loss: -.

Primary source

https://twitter.com/sherlockdefi/status/1764879891072200880 ↗

Sourced from

slowmist

Technical record