A $36M loss where no smart contract was exploited, no bridge was broken, and no code was hacked.
The entry point was a phishing email. The reason it cost $36M instead of a password reset was that production keys had been backed up onto the laptop that opened it.
The email
In June 2026, an employee at Humanity Protocol received a message that appeared to come from Bithumb, a Korean exchange. The attachment was labelled as a token lockup schedule update.
It was malware. The laptop was compromised.
That alone is an ordinary bad day. Phishing succeeds constantly, and every team in this industry has received a message like it. The question that determines the damage is always the same: what was on that machine?
The answer was the entire trust root
During the previous year's mainnet launch, production keys had been inadvertently backed up onto that employee's laptop:
- Admin hot wallet keys.
- A quorum of multisig owner keys, across both chains.
Read that second line again. Not one key. A quorum. Multisig exists precisely to remove single points of failure, and a quorum sitting on one internet-connected laptop converts a 3-of-5 into a 1-of-1.
One email. One laptop. $36M.
Quantstamp attributed the operation to North Korea's Lazarus Group. The same actors were behind Drift Protocol's $285M, which began with a six-month social engineering campaign, and Kelp DAO's $292M, which came through a compromised LayerZero RPC node.
In April 2026 alone, North Korea-linked actors took $578M of the $634M lost across crypto. That figure is not a rounding error. It is 91% of the month.
What the founder said
Terence Kwok, Humanity Protocol's founder, put it plainly:
"The hard lesson here is that operational security is as critical as smart-contract security, and we're rebuilding accordingly."
That is the correct conclusion, and it arrived from the worst possible teacher.
The reason it is worth repeating is that most teams still treat OpSec as a checklist someone else owns. Smart contract security gets audits, bug bounties, formal verification, monitoring. Key custody gets a Confluence page and a "we'll tighten it up before mainnet" note that nobody reads again.
The asymmetry nobody prices in
Look at the direction of the 2026 numbers.
Losses per protocol exploit have fallen sharply: from an average of about $156M per incident in 2020 to 2022, to roughly $14M from 2023 onward. Contracts genuinely are harder to break. That work paid off.
But the edges exploded. H1 2026 saw 182 incidents, up about 50% year over year, for roughly $956M in total losses. Wallet compromises accounted for $444M+ of that. Bridges $328M+. Supply chain $298M+.
Of the 182 incidents, contract vulnerabilities were the most common category with 85. Key compromises were only 17 incidents, and produced the most damage per incident by a wide margin.
That is the whole shape of the problem in one sentence: cheap mistakes are frequent, expensive mistakes are operational, and the expensive kind is what actually moves the total.
The five things worth doing this week
If you hold keys for anything that matters, this is the list, ordered by how much damage the absence of it causes:
1. Production keys never touch a personal device.
Not a laptop, not a phone, not a "secure" USB in a drawer. If it can reach email, it can reach an attacker.
2. Hot wallet keys live in an HSM.
The point of a hardware security module is that the key does not exist in a file that can be copied. A key file on a machine is a key file on a machine, no matter how good the machine is.
3. Device-level security for anyone with key access.
MDM, disk encryption, patching, and a rule that key-holders do not open attachments from exchanges. The laptop that ends a company is almost always the unremarkable one belonging to someone with the right access and no training.
4. Phishing drills that use the real thing.
Fake exchange notices about token lockups, vesting schedules, and compliance updates are the highest-yield template in crypto, because they play on schedule anxiety that every project has.
5. Assume the laptop is already compromised.
This is the one that actually changes architecture. If you design as though any single employee machine is hostile, then keys on it become an obviously insane idea, and the quorum stops being a formality you can reconstruct from memory.
The $36M question
The uncomfortable part is not that Humanity Protocol got phished. Most teams would fail the same test.
The uncomfortable part is the second event: a quorum of multisig keys was restored onto a laptop during a launch, and then stayed there for a year, through audits, through reviews, through whatever operational security checklist the company had.
Nobody asked where those keys were, because everyone assumed someone else knew.
If you are honest with yourself, you already know whether your answer is different.
The archive. 61 on-chain investigations and 64 days of GitHub leak scanning, redacted and never used. Read the index or try the free token risk check at qanzhi111.github.io.


Top comments (0)