BlackHart
Go live
Hacks feed/Fogo Foundation

Fogo Foundation

August 28, 2026·Fogo·Key Compromise
$3.0M
total loss
StatusConfirmed

Why it happened

Attack class: Access control

Foundation wallets validly signed 400M FOGO to a fresh wallet.

What would have stopped it

  • Require independent multisig approval on every large treasury transfer.
  • Allow-list treasury destinations and delay transfers to new addresses.

Not scored before the exploit

BlackHart had not scored Fogo Foundation before this exploit.

Someone took over Fogo Foundation wallets and sent 400 million FOGO, about $3 million and 4 percent of genesis supply, to their own wallet on August 28. The Foundation has not said how. User funds on the network were not affected, and the chain kept running until validators halted it the next day to freeze the attacker's addresses. When Fogo restarted on September 2 it had recovered and removed 237 million of the stolen tokens. The other 163 million, about $1.2 million, had already been spread across other wallets and is being chased with exchanges and law enforcement.

User funds on Fogosafe
Fogo consensus and programssafe(chain halted on purpose, restarted September 2)
Foundation treasurydrained(400M FOGO, about $3M)
Recovered tokenspartially affected(237M FOGO removed from supply, 163M still out)
Exploit anatomy

Two Fogo Foundation wallets sent 400 million FOGO to a fresh receiving wallet, the largest piece in a 240 million FOGO transfer, before about half was spread out through a dispersal wallet.

The attack in 4 steps. Step 1, Root control: Foundation wallet A (source), Foundation wallet B (source). Step 2, Collect: Receiving wallet (hub), about $3M reached this step. Step 3, Dispersal: Dispersal wallet (hub), about $1.5M reached this step. Step 4, Halt: Restricted and removed (exit), about $3M reached this step.

  1. Step 1: Root control

  2. Step 2: Collect

  3. Step 3: Dispersal

  4. Step 4: Halt

    • Exit
      Restricted and removed
      237M FOGO taken out of supply
      163M FOGO still outstanding

Why each step worked

    • Foundation signing compromisedvector not disclosed
    • No second approvermissing control400M FOGO to a wallet created that day
    • No destination allow-list or delaymissing controlfresh address accepted at once
    • Eleven hours to disclosuremissing controloutflows not caught in real time
    • Validator halt and address restrictionsmall validator set upgraded the chain
Full forensic detail

Step-by-step reconstruction, root cause, counterfactuals, remediation, and disclosure timeline.

Exploit anatomy

1.
An unknown actor gained the ability to sign transfers from Fogo Foundation wallets. The Foundation has not said whether keys, a signing system or a person were compromised.
2.
On August 28, 2026, a Foundation-held wallet sent a 100 FOGO test transfer at 14:04:05 UTC to a fresh receiving wallet, then two transfers of 80 million FOGO each at 14:13 and 14:44 UTC. All three used durable-nonce transactions, the same format the wallet used for its routine transfers.
3.
At 15:39:51 UTC a second Foundation wallet, topped up with about 145 million FOGO seven minutes earlier, sent 240 million FOGO to the same receiving wallet. That brought the total to 400 million FOGO, about $3 million and 4 percent of genesis supply.
4.
Over the next ten hours the receiving wallet sent about 200 million FOGO to a dispersal wallet, which split it into dozens of smaller transfers. Between 00:57 and 01:00 UTC on August 29 it pushed the remaining 200 million into three fresh wallets, minutes before the Foundation's 01:13 UTC disclosure.
5.
Around 15:30 UTC on August 29 the validators halted Fogo mainnet and upgraded it to restrict the addresses tied to the incident. When the chain restarted on September 2, Fogo said 237 million FOGO had been recovered and permanently removed from supply. The remaining 163 million FOGO, about $1.2 million, had left before the halt and is being pursued with exchanges and law enforcement.

Root cause

The Fogo Foundation lost control of who could authorize transfers from its treasury wallets. The Foundation says an unknown actor compromised the organization; it has not published the vector. No Fogo program or consensus flaw was involved: the chain was not attacked and kept running normally for about fifteen hours after the theft. On-chain, the 400 million FOGO left two Foundation wallets in transactions that each wallet validly signed, in the same pattern the Foundation used for its routine transfers (a small test, then the main amount, through durable-nonce transactions). The second wallet was topped up minutes before its 240 million FOGO transfer. Both wallets kept being used for Foundation transfers after the restart. That pattern fits an attacker steering the Foundation's own signing workflow, but it does not show whether keys, signing infrastructure or staff were the point of entry, and Fogo has not said. What contained the loss was not a wallet control but chain-level power: a small validator set halted the network and upgraded it to restrict the attacker's addresses, which let Fogo remove 237 million of the 400 million FOGO from supply.

Prevention analysis

Require independent multisig approval on every large treasury transfer.

A second approver checking the destination would have had to sign 400 million FOGO going to a wallet created that day.

Allow-list treasury destinations and delay transfers to new addresses.

The receiving wallet had never been used before. A delay on first-time destinations would have held the funds long enough to catch the theft before any FOGO moved on.

Watch treasury outflows in real time.

About 163 million FOGO left the receiving wallet in the eleven hours before disclosure. Faster detection would have shrunk the part that could not be recovered.

Similar incidents

KITE Foundation (2026)

Foundation-linked token wallets were drained in one burst, and the team voided the stolen tokens with a protocol-level freeze rather than a wallet control.

Drift Protocol (2026)

Privileged operational signing was turned against the protocol, with pre-signed durable-nonce transactions in the picture. Same class: weak control over what the organization's own signers approve.

Remediation

1.The Fogo Foundation alerted exchanges, law enforcement and forensic specialists on August 28, 2026.
2.Validators halted Fogo mainnet on August 29 and upgraded the network to restrict the addresses tied to the incident.
3.Fogo restarted mainnet on September 2 after recovering and permanently removing 237 million FOGO from supply.
4.Pending: recovery of the remaining 163 million FOGO with exchanges and law enforcement, and a public post-incident report on the vector and the changes to treasury custody.pending
5.Other foundations should put large treasury transfers behind independent approvals and destination allow-lists rather than relying on a chain halt.

Timeline

2026-08-28A Foundation wallet sends a 100 FOGO test transfer to a fresh receiving wallet.
2026-08-28First 80 million FOGO transfer to the receiving wallet.
2026-08-28Second 80 million FOGO transfer.
2026-08-28Onward transfers begin toward a dispersal wallet; about 200 million FOGO leaves over ten hours.
2026-08-28A second Foundation wallet sends 240 million FOGO, bringing the total to 400 million.
2026-08-29The remaining 200 million FOGO is moved into three fresh wallets.
2026-08-29Fogo Foundation discloses the compromise and says the chain is unaffected.
2026-08-29Fogo says mainnet was halted within the past hour to stop movement of the affected assets.
2026-09-02Mainnet restarts; 237 million FOGO recovered and removed from supply, 163 million still being pursued.
Fogo Foundation. Fogo validator set. The Block. BlackHart on-chain reconstruction
Continuous adversarial monitoring

Get your protocol scored across 12 dimensions, or request ongoing coverage.