Has Sky Protocol Ever Been Hacked? The Honest Record
No known exploit has drained its core contracts. The record also holds Black Thursday and real risks worth weighing before you trust it.
In March 2020, bots won millions of dollars in ETH collateral from MakerDAO for bids of zero. That episode, remembered as Black Thursday, sits at the center of any honest answer to whether Sky Protocol has been hacked. So here is the direct answer.
No known exploit has drained Sky Protocol’s core smart contracts, and the savings module has run since 2019 without a contract-level incident. The protocol still carries real risk, so treat that clean contract record as one input to weigh, never a clean bill of health.
That nuance is the whole story. The code is open source and has been audited repeatedly by firms including ChainSecurity, Cantina, and Spearbit, backed by a public bug bounty on Immunefi. Black Thursday in 2020 was a liquidation-design and oracle-lag failure during a market crash, and it was not a contract exploit. Sky Protocol traces its lineage to MakerDAO, one of DeFi’s longest-running systems, whose core stablecoin contracts have operated without an exploit.
Emergency Shutdown and a governance pause delay exist as safeguards, and residual risks remain across smart-contract, oracle, governance, freeze-function, and peg dimensions. Read the record, then judge it for yourself. Verify, don’t believe.
Has Sky Protocol ever been hacked?
Sky Protocol has no known protocol-level exploit, and it is not risk-free. No known hack has drained its core smart contracts, and the savings module that pays the Sky Savings Rate has operated since 2019 without a contract-level incident. That is a genuine strength earned over years of live operation across MakerDAO and now Sky.
Say the harder part just as plainly. “No known exploit” is a description of the record so far, and it does not mean the contracts cannot be exploited. No onchain protocol is risk-free. The value of the record is that you can check it against primary sources rather than take anyone’s word for it.
No known exploit has drained Sky Protocol’s core contracts, and the protocol is still not risk-free.
What about Black Thursday?
Black Thursday, on March 12, 2020, was the one severe stress event in the record, and it was a design failure rather than a contract hack. A sharp market crash sent Ethereum gas prices up by an order of magnitude, the network congested, and the price oracle feeding Maker lagged the real market.
Liquidation auctions cleared with winning bids of zero DAI because most keeper bots ran the same inflexible script and could not bid under the gas spike. One participant won roughly $8.3 million in ETH collateral for almost nothing, and the system was left with several million dollars of bad debt while liquidated users lost collateral.
The contracts did what they were told. The failure lived in the oracle timing, network conditions, and auction design, so this was a risk-management gap and not an exploit of the code. The community later declined full compensation for affected users and redesigned the liquidation system with a new collateral auction model.
Black Thursday was a liquidation-design and oracle failure during a market crash, not a contract hack.
What security does Sky Protocol have?
Sky Protocol reduces risk through open-source code, repeated independent audits, a bug bounty, and emergency controls. Each measure lowers risk without removing it, which is the correct way to read any security posture.
Open source and repeatedly audited
The codebase is public and has been audited by firms including ChainSecurity, Cantina, and Spearbit, with review work continuing on newer cross-chain and governance modules. Audits catch bugs before they ship, and they never guarantee safety. Most exploited contracts across DeFi had also been audited, so an audit is evidence of diligence rather than a seal of invulnerability.
An active bug bounty
Sky runs a public bug bounty program on Immunefi that pays researchers to disclose vulnerabilities responsibly. A standing bounty signals an ongoing security posture and a live channel for outside eyes on the code, which is a sign of process rather than a promise of outcome.
Emergency controls
The protocol has an Emergency Shutdown mechanism and a governance pause delay. Emergency Shutdown can wind the system down in an orderly way and return collateral to holders in a severe event. The pause delay gives the community time to respond before a malicious or mistaken governance action takes effect.
Where the risks still are
The residual risks are smart-contract, oracle, governance, the freeze function, and peg risk. Naming them plainly is the point.
- Smart-contract risk. Any onchain protocol can contain undiscovered bugs. Audits and a bug bounty lower this risk, and they cannot remove it.
- Oracle risk. The protocol depends on price oracles. Black Thursday showed how oracle lag under stress can cause real losses, which is why the oracle and liquidation design were rebuilt afterward.
- Governance attack surface. Concentrated voting power or compromised tooling is a real concern, and there has been documented scrutiny over multisig tooling and reserves managed through external accounts. The pause delay and Emergency Shutdown are the mitigations.
- The freeze function. USDS carries a freeze capability, so it is not censorship-resistant. That is an honest centralization consideration to weigh, and self-custody protects your keys, not the token’s controls.
- Peg risk. If USDS traded away from its target, that stress could cascade to sUSDS redemption value. The Peg Stability Module is the main defense, and depegs happen for readable reasons.
For a transparency signal rather than a safety badge, Sky became the first DeFi protocol to earn an S&P Global credit rating, a B- with a stable outlook. S&P flagged depositor concentration, centralized governance, and a thin capital buffer. A published rating with disclosed concerns tells you more than any adjective would, and what a B- signals and does not signal is worth reading in full.
The record at a glance
Read across three layers. The core smart contracts, including vaults and the savings module running since 2019, have no known protocol-level exploit and are covered by repeated audits and a bug bounty.
Get Kush’s stories in your inbox
Join Medium for free to get updates from this writer.
Black Thursday on March 12, 2020 let liquidation auctions clear at zero during a market crash with oracle lag and congestion, a design failure rather than an exploit, and the liquidation system was later redesigned.
Governance and operations security carries documented scrutiny over multisig tooling and externally managed reserves, with no exploit of funds, addressed through Emergency Shutdown and the pause delay.
The pattern is a contract layer with no known exploit, one serious stress event that was a design failure, and ongoing governance questions the protocol answers with audits, a bounty, and emergency mechanisms. That is a record to weigh, not a safety guarantee.
How to verify this yourself
You do not have to take this account on faith. Check it against primary sources.
- Read the published audit reports from the named firms and check each report’s date and scope.
- Review the live contract registry and deployment addresses through Sky’s chainlog.
- Check the Immunefi bug bounty page for the program’s scope and any disclosed findings.
- Read the protocol’s user risk documentation and the Black Thursday post-mortems for the primary account.
Final thought
The most useful answer to whether Sky Protocol has been hacked is the one that survives scrutiny. A clean contract record over years is meaningful, and Black Thursday is proof that design and market conditions can hurt users even when the code holds.
What earns trust here is that every claim above can be checked against audits, post-mortems, and onchain data. If you want to put stablecoins to work after weighing that, start at the baseline and understand the risks first, then explore sky.money with eyes open.
What matters more to you when judging a protocol’s security: the length of its track record, or how honestly it discloses its risks?
Frequently asked questions
Has Sky Protocol ever been hacked?
There is no known hack that exploited its core smart contracts to drain the protocol, and the savings module has run since 2019 without a contract incident. It is not risk-free, and the record should be weighed rather than treated as a guarantee.
Was Black Thursday a hack?
No. It was a liquidation-design and oracle-lag failure during a March 2020 market crash that let auctions clear at zero. Users lost collateral, the system took on bad debt, and the liquidation model was redesigned afterward.
Is Sky Protocol audited?
Yes. The open-source code has been audited by firms including ChainSecurity, Cantina, and Spearbit, and it is backed by a public bug bounty on Immunefi. Audits reduce risk rather than remove it.
Can Sky Protocol be hacked in the future?
Like any onchain protocol, yes in principle. Smart-contract, oracle, and governance risks remain, which is exactly why audits, a bug bounty, and emergency controls exist.
Can USDS be frozen?
USDS has a freeze function, so it is not censorship-resistant. That is an honest centralization consideration to weigh alongside the protocol’s strengths.
How can I check the record myself?
Read the audit reports, the chainlog contract registry, the Immunefi bug bounty scope, and the protocol’s user risk documentation directly. The record is public, which is the point.
