VERDICT —OUT OF SCOPE
Root cause is private-key / signer compromise — the on-chain contract behaved exactly as written. No pre-deployment source audit or bytecode review reaches the key-custody perimeter; this is operational-security territory (HSM/MPC hygiene, key rotation, hot-wallet isolation). Bytecode would show nothing wrong.
▰ METHOD
PRIVATE KEY
PRIVATE-KEY
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
Sentinel founder Serpent tweeted that OpenSea's official Discord was attacked. Hackers used bot accounts to post fake links in the channel, and said that "OpenSea has reached a cooperation with YouTube. Click the link to participate in the mint pass NFT limited to 100 pieces." Users should be aware of the risks and do not click on links provided by hackers. Attack method (per SlowMist): Account Compromise. Reported loss: -.
Primary source
https://twitter.com/Serpent/status/1522494914550181888 ↗Sourced from
slowmist
Technical record
- chain
- —
- protocol
- OpenSea
- bug_class
- private-key
- date_occurred
- 2022-05-06
- loss_usd
- —
- source_id
- sm:opensea::2022-05-06
Related — same bug class· private-key