Cyber·Monitoring
Shai-Hulud Supply-Chain Attack Trojanizes 19 PyPI Packages
PyPI repository (global online service)· Global4 Jun
7 reportsPROPCYCAS
MediumAI Refreshed
Developing event. Generated by AI and subject to further corroboration and review.
DevelopingLow impactAI Refreshed
Humanity Protocol Token Crashes 80% After $32M Private-Key Hack
Occurred 9 Jun 2026·Detected 13 Jun 2026·
Cryptocurrency / blockchain — no specific physical location2 reports
CyberCyber
A reported private-key compromise on the Humanity Protocol blockchain project caused the project's H token to fall more than 80% in value. Two mainstream crypto-news outlets describe approximately $30–32 million of crypto-asset theft tied to the wallet compromise. No insured custodian, exchange, or institutional counterparty has been identified in the available evidence, and no London-market loss pathway is established.
AI-generated from linked source reports. See our correction policy.
Impact verdict
Low impact. Sources describe a single-project token-level private-key compromise with a ~$30–32M theft figure. No custodian, exchange, or institutional wallet provider is named as having absorbed the loss, the loss magnitude sits well below thresholds typically associated with multi-syndicate London specialty action, and a token price collapse is not itself an insured loss. No source ties the event to a London specialty line. Materiality remains low pending evidence of an insured counterparty exposure.
View assessment methodologyHow we grade what we know -- Known · Reported · Uncertain. Methodology →
Intelligence ledger
Each line expands in place to its underlying sourced claim.
Known10 lines
Humanity Protocol token crashed more than 80%▾
structured lineknown
No separate sourced-claim record is available for this line yet.
Cause was a private-key hack valued at $32 million▾
structured lineknown
No separate sourced-claim record is available for this line yet.
Event occurred on or around June 9, 2026▾
structured lineknown
No separate sourced-claim record is available for this line yet.
The reported private-key compromise and token price collapse occurred on or around 9 June 2026.▾
event_date_june_2026contextvalid from 9 Jun 2026, 00:00Cyber
The event is classified as a cyber theft / private-key compromise targeting a blockchain/cryptocurrency project; no physical infrastructure impact is reported.▾
event_cause_classificationcontextvalid from 9 Jun 2026, 07:45
Market relevance: Low
The Humanity Protocol H token fell by more than 80% following the reported private-key compromise.▾
h_token_price_declinedamagevalid from 9 Jun 2026, 00:00Cyber
Market relevance: low
The Humanity Protocol (H) token price fell more than 80% following the private-key compromise, with cointelegraph.com specifying an 85% decline.▾
humanity_protocol_token_price_crashnone identifiedvalid from 9 Jun 2026, 00:00
Market relevance: Token price collapse is not an insured loss; no counterparty named
Supersession history: 1 prior/revised claim rows.
A private-key compromise was reported against the Humanity Protocol blockchain project.▾
event_private_key_compromise_humanity_protocolfactvalid from 9 Jun 2026, 00:00Cyber
Market relevance: low
“Humanity Protocol token crashes more than 80% after a $32 million private-key hack” — coindesk.com · 9 Jun 2026, 07:45 · mainstream media
“Humanity Protocol Hacked, H Token Crashes 85%” — cointelegraph.com · 9 Jun 2026, 03:30 · mainstream media
No source-grounded evidence links the Humanity Protocol private-key compromise to a London specialty insurance exposure, insured custodian, or exchange counterparty.▾
london_market_loss_pathway_not_establishednone identifiedvalid from 13 Jun 2026, 23:38
Market relevance: Materiality remains low; no insured loss pathway identified
“no evidence of broader critical infrastructure impact or insured corporate losses relevant to London market books” — cointelegraph.com · 9 Jun 2026, 03:30 · mainstream media
Humanity Protocol suffered a private-key compromise on or around 9 June 2026.▾
humanity_protocol_private_key_hack_eventnone identifiedvalid from 9 Jun 2026, 00:00
Market relevance: Indirect — crypto project theft without identified insured counterparty
“Humanity Protocol token crashes more than 80% after a $32 million private-key hack” — coindesk.com · 9 Jun 2026, 07:45 · mainstream media
“Humanity Protocol Hacked, H Token Crashes 85%” — cointelegraph.com · 9 Jun 2026, 03:30 · mainstream media
Reported8 lines
$32 million is the value of the private-key compromise▾
structured linereported
No separate sourced-claim record is available for this line yet.
Available sources do not indicate broader critical-infrastructure disruption, exchange outage, or multi-project contagion arising from the compromise.▾
no_broader_infrastructure_disruptionnone identifiedvalid from 13 Jun 2026, 23:38
Market relevance: Limits systemic exposure assessment for London cyber/crime books
“crypto-specific cyber theft with no evidence of broader critical infrastructure impact” — cointelegraph.com · 9 Jun 2026, 03:30 · mainstream media
Supersession history: 1 prior/revised claim rows.
Sources place the value of the private-key compromise at approximately $30–32 million.▾
theft_value_private_key_compromiselossvalid from 9 Jun 2026, 00:00Cyber
Market relevance: low
The private-key hack is reported by coindesk.com as a $32 million event.▾
humanity_protocol_theft_value_usd_32mnone identifiedvalid from 9 Jun 2026, 00:00
Market relevance: Theft confined to protocol; no insured counterparty named in sources
Cointelegraph.com reports the private-key compromise resulted in approximately $30 million in losses.▾
humanity_protocol_theft_value_usd_30mnone identifiedvalid from 9 Jun 2026, 00:00
Market relevance: Theft confined to protocol; no insured counterparty named in sources
The private-key compromise is reported at $32 million by a single mainstream source.▾
private_key_hack_value_32mlossvalid from 9 Jun 2026, 07:45
Market relevance: Low: no insured party or custodian identified; not anchored to a London specialty loss pathway
The event record is currently grounded in a single mainstream crypto-press article; no corroborating authoritative, trade, or wire sources are present.▾
source_basis_single_mainstreamothervalid from 13 Jun 2026, 23:37
Market relevance: Low
The hack and token crash were reported on or around 9 June 2026 by a single mainstream source.▾
event_date_observedstatusvalid from 9 Jun 2026, 07:45
Market relevance: Low
Uncertain8 lines
Identity of the attacker(s)▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Whether any insured custodial or exchange entity absorbed the loss▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
Whether any London-market insured digital-asset custodian, exchange, or service provider is exposed▾
structured lineuncertain
No separate sourced-claim record is available for this line yet.
No insured custodian, exchange, or institutional counterparty is identified in the available source set as having absorbed any portion of the loss.▾
no_insured_counterparty_identifiednone identifiedvalid from 13 Jun 2026, 23:38
Market relevance: Critical for London market materiality assessment
No source-grounded evidence identifies an insured custodian, exchange, or London-market-insured digital-asset service provider absorbing any portion of the $32M loss.▾
insured_custodian_exposure_unconfirmedloss
Market relevance: Low: absence of an insured party caps London market materiality
No London-market loss pathway is established by the available evidence; the event is a project-level crypto theft with no identified insured exposure.▾
london_market_loss_pathwayno identified pathwayvalid from 14 Jun 2026, 09:08Cyber
Market relevance: low
The identity of the attacker(s) responsible for the reported private-key compromise is not identified in the available evidence.▾
attacker_identity_unknownstatusvalid from 14 Jun 2026, 09:08Cyber
Supersession history: 1 prior/revised claim rows.
No source identifies an insured custodian, exchange, or institutional wallet provider that absorbed loss from this event.▾
insured_counterparty_identifiedstatusvalid from 14 Jun 2026, 09:08Cyber
Market relevance: low
“no evidence of broader critical infrastructure impact or insured corporate losses relevant to London market books” — cointelegraph.com · 9 Jun 2026, 03:30 · mainstream media
Latest developments
- Impact rationale refreshed from cited evidence.
- Mainstream crypto press reported a private-key compromise affecting Humanity Protocol. — coindesk.com
- Crypto press estimated the theft at roughly $30–32 million; figures vary slightly between outlets. — coindesk.com
- The H token declined more than 80% (one outlet reports 85%) in the immediate aftermath of the reported compromise. — coindesk.com
- The reported incident occurred on or around 9 June 2026. — coindesk.com
- No insured counterparty has been identified in the available evidence. — coindesk.com
- No London-market loss pathway is established by available evidence. — coindesk.com
- The attacker(s) have not been identified in the available evidence. — coindesk.com
Timeline
Status Change13 Jun 2026, 23:38
Status changed to developing
evidence_trigger: corroboration >= 2
signal -> developing
Corroboration13 Jun 2026, 23:38
Humanity Protocol suffered a private key compromise resulting in approximately $30M in losses, causing its H token to crash 85%. The incident is a crypto-specific cyber theft with no evidence of broader critical infrastructure impact or insured corporate losses relevant to London market books.
Source: cointelegraph.com (Mainstream Media) · View source
Initial Detection13 Jun 2026, 23:37
Initial Detection
A $32 million private-key hack caused the Humanity Protocol token to crash more than 80%. The incident is a cyber theft targeting a blockchain/cryptocurrency project with no evidence of broader infrastructure impact or insured loss pathways relevant to the London specialty market.
Humanity Protocol token crashes more than 80% after a $32 million private-key hack
Source: coindesk.com (Mainstream Media) · View source
Lloyd's classifications
Tracking this kind of risk? Get an email when Cyber events escalate.
Get alerts