{"investigation":{"slug":"hegicold-contract","entity_name":"Hegic(old contract)","trust_score":30,"severity_base":null,"score_modifier":0,"confidence":0.82,"status":"published","content_type":"investigation","summary":"Hegic is an anonymous-founded, Ethereum-based decentralized options trading protocol originally launched in April 2020. The original (v1) smart contract suffered a critical code defect within hours of mainnet deployment that permanently locked user funds, compounded by misrepresentation of the pre-launch security review. A separate deprecated contract from January 2022 was additionally exploited in February 2025, draining approximately $80,000 in WBTC. While affected users were reimbursed out of team funds in both incidents, the underlying contracts remain permanently compromised.","sections":[{"content":"Hegic is a non-custodial, peer-to-pool on-chain options trading protocol built on Ethereum. It was conceived and developed by an anonymous individual operating under the pseudonym '0MOLLY WINTERMUT3' (referred to publicly as Molly Wintermute), who described herself as a person with no prior social capital or reputation in the crypto space. The protocol allows users to buy and write call and put options on ETH and Wrapped Bitcoin (WBTC) without KYC requirements. Hegic was announced on the EthResearch forum in February 2020 and initially deployed to mainnet on April 23, 2020. Following the critical bug incident described below, the protocol was relaunched and iterated through several versions, including a beta mainnet release branded 'Hegic v888' in October 2020. The native governance and utility token, HEGIC, launched on September 9, 2020, with a fixed total supply of approximately 3.012 billion tokens distributed across early contributors (20%), a development fund (10%), liquidity mining and utilization rewards (40%), a bonding curve (25%), and a Balancer pool (5%). The entity investigated here specifically concerns the original v1 contract deployed in April 2020 and the deprecated January 2022 contract, both of which suffered critical security failures.","heading":"Protocol Overview","sources":[{"url":"https://iq.wiki/wiki/hegic","name":"iq.wiki","type":"other","credibility":3},{"url":"https://medium.com/hegic/announcing-hegic-token-liquidity-mining-utilization-rewards-and-staking-d1dd6605f2cd","name":"medium.com","type":"other","credibility":3},{"url":"https://decrypt.co/35038/hegics-molly-wintermute-im-paying-a-high-price-for-the-mainnet-first-approach-to-building","name":"decrypt.co","type":"other","credibility":3}],"severity":"medium"},{"content":"On April 23, 2020, Hegic deployed its v1 smart contract to Ethereum mainnet. Within hours, a critical defect was discovered that permanently prevented users from withdrawing funds from expired options contracts. The defect stemmed from a function call using the identifier 'OptionIDs' rather than the correct 'OptionsIDs' — a single missing letter 's' — in the liquidity unlocking mechanism. Because the function referenced a non-existent identifier, the contract's withdrawal logic was rendered permanently inoperable for any options that expired under that contract. Approximately $28,000–$48,000 in user funds (denominated in ETH and DAI) across 19 unexercised options contracts (3 calls and 16 puts) became permanently inaccessible. The affected funds cannot be recovered by any means; they remain locked on-chain to this day. Hegic founder Molly Wintermute initially characterized the incident publicly as a 'typo,' a framing that drew significant criticism from the security community. Trail of Bits CEO Dan Guido stated: 'It's clearly an error, and one that would have been easily caught had they written any unit tests.' Wintermute subsequently issued a public apology for the 'typo' framing, acknowledging it should have been described as a bug or security issue. The protocol was taken offline the day after launch, on April 24, 2020, and a new contract was deployed. Hegic founder Molly Wintermute pledged and subsequently executed 100% reimbursement of all affected users from personal and contributor funds, though the original locked assets remain permanently inaccessible in the v1 contract.","heading":"Critical Bug: Permanently Locked Funds at Launch (April 2020)","sources":[{"url":"https://decrypt.co/26725/hegic-backpedals-on-typo-claim","name":"decrypt.co","type":"other","credibility":3},{"url":"https://cryptobriefing.com/defi-bug-freezes-30000-ether-forever/","name":"cryptobriefing.com","type":"other","credibility":3},{"url":"https://cryptonews.net/news/security/314071/","name":"cryptonews.net","type":"other","credibility":3},{"url":"https://davidgerard.co.uk/blockchain/2020/04/26/the-dforce-and-hegic-defi-exploits-and-why-smart-contracts-are-bad/","name":"davidgerard.co.uk","type":"other","credibility":3}],"severity":"medium"},{"content":"Before the April 2020 mainnet launch, Hegic engaged Trail of Bits for a code review. Trail of Bits conducted a three-day review — not a full audit — and identified ten critical flaws in the codebase. According to Trail of Bits CEO Dan Guido, the firm explicitly recommended delaying the deployment and communicated the severity of the identified issues. Hegic patched only a subset of the flagged flaws and proceeded with launch. Critically, Hegic publicly described the Trail of Bits engagement as an 'audit,' a characterization Trail of Bits disputed: the firm stated it had performed a '3-day code review' and that Hegic had 'misrepresented our 3-day code review as an audit, then immediately deployed.' The defect that resulted in permanently locked funds was among the issues that would have been caught by standard unit testing, according to Guido. This sequence — receiving critical pre-launch warnings, failing to remediate all identified issues, proceeding with deployment against the reviewer's recommendation, and misrepresenting the nature and scope of the security review — represents a serious failure of pre-launch security governance. This incident is frequently cited in DeFi security literature as an example of audit theater, where a limited code review is promoted as a comprehensive security certification to build user confidence without the substance to support it.","heading":"Audit Misrepresentation and Pre-Launch Security Failures","sources":[{"url":"https://kermankohli.substack.com/p/hegic-vs-trail-of-bits-and-the-issue","name":"kermankohli.substack.com","type":"other","credibility":3},{"url":"https://decrypt.co/26725/hegic-backpedals-on-typo-claim","name":"decrypt.co","type":"other","credibility":3},{"url":"https://www.publish0x.com/interestingcrypto/hegic-case-48-dollars-000-cents-typo-or-why-dofi-protocols-n-xejoomg","name":"publish0x.com","type":"other","credibility":3},{"url":"https://davidgerard.co.uk/blockchain/2020/04/26/the-dforce-and-hegic-defi-exploits-and-why-smart-contracts-are-bad/","name":"davidgerard.co.uk","type":"other","credibility":3}],"severity":"medium"},{"content":"On February 23, 2025, a second security incident involving Hegic infrastructure was identified and flagged by blockchain security firm BlockSec. The targeted contract was a deprecated WBTC Puts Pool contract originally deployed on January 4, 2022 — nearly three years prior to the exploit. The contract had seen almost no interaction since its deployment and is believed to have been a test or staging contract rather than a live production contract. Despite its apparent dormancy, the contract held 1.1 WBTC (worth approximately $80,000 at time of exploit) that had been sent to it from the Hegic Deployer address and was never fully decommissioned. The attacker exploited a vulnerability in the `withdrawWithoutHedge` function: the variable `t.share` was not updated after each withdrawal call, and a critical state validation check had been commented out of the code, removing a key safeguard. This allowed the attacker to repeatedly call the withdrawal function within a single transaction loop, extracting the full contract balance. Hegic issued a security report via Discord and confirmed via its official Twitter/X account that the current architecture (implemented October 2022 and forward) was not affected and remained secure. A bug bounty program was announced following the incident. The Verichains security research blog published a detailed post-mortem. The incident illustrates the risk of leaving funded legacy contracts active without decommissioning them once they are no longer in use.","heading":"Deprecated Contract Exploit: $80,000 WBTC Drained (February 2025)","sources":[{"url":"https://blog.verichains.io/p/hegic-options-protocol-how-a-deprecated","name":"blog.verichains.io","type":"other","credibility":3},{"url":"https://x.com/HegicOptions/status/1896933787923345470","name":"x.com","type":"other","credibility":3},{"url":"https://www.nominis.io/insights/crypto-security-incidents-march-2025","name":"nominis.io","type":"other","credibility":3}],"severity":"medium"},{"content":"Hegic was conceived, built, and operated by a single anonymous developer using the pseudonym 'Molly Wintermute' (stylized '0MOLLY WINTERMUT3'). No real identity has been publicly disclosed. Wintermute has stated: 'The crypto community can only judge me by what they can see by themselves in my code that is open sourced on GitHub, on the interfaces of Hegic website or by reading the community members' comments.' This single-developer, anonymous architecture presents elevated operational risk: there is no legal entity, no identified responsible party for regulatory or legal accountability, and no organizational redundancy if the developer ceases to maintain the protocol. In an interview with Decrypt following the April 2020 incident, Wintermute acknowledged: 'I'm paying a high price for the mainnet-first approach to building.' The protocol's history of deploying to mainnet ahead of completed security remediation, combined with its anonymous single-developer structure, contributes to its elevated risk profile. The GitHub repository for the old contracts (hegic/old-contracts) remains publicly accessible, archiving the original ETH Put Hedge Contract and DAI Liquidity Pool Contract that contained the critical defect.","heading":"Developer Anonymity and Operational Risk","sources":[{"url":"https://decrypt.co/35038/hegics-molly-wintermute-im-paying-a-high-price-for-the-mainnet-first-approach-to-building","name":"decrypt.co","type":"other","credibility":3},{"url":"https://golden.com/wiki/Molly_Wintermute-REPY4D8","name":"golden.com","type":"other","credibility":3},{"url":"https://github.com/hegic/old-contracts","name":"github.com","type":"other","credibility":3}],"severity":"medium"},{"content":"In the April 2020 incident, Hegic founder Molly Wintermute committed to and executed full reimbursement of all affected users — both liquidity providers (compensated with premiums paid) and options holders (compensated for any losses on existing positions). The reimbursements were funded personally by Wintermute and early contributors. The protocol was relaunched under a corrected contract in May 2020. Despite the reimbursement, the originally locked funds remain permanently inaccessible in the v1 contract; no technical recovery is possible. In the February 2025 deprecated contract exploit, the drained 1.1 WBTC represented funds held by the deployer address rather than active user deposits, meaning live user funds were not affected. Hegic confirmed that no user funds in active contracts were lost. However, the pattern of multiple security failures across the protocol's history — a critical launch-day bug resulting in permanent fund loss, followed years later by a second exploit of an insufficiently decommissioned legacy contract — raises questions about the protocol's ongoing security governance practices.","heading":"User Impact and Reimbursement","sources":[{"url":"https://decrypt.co/26725/hegic-backpedals-on-typo-claim","name":"decrypt.co","type":"other","credibility":3},{"url":"https://blog.verichains.io/p/hegic-options-protocol-how-a-deprecated","name":"blog.verichains.io","type":"other","credibility":3},{"url":"https://cryptobriefing.com/defi-bug-freezes-30000-ether-forever/","name":"cryptobriefing.com","type":"other","credibility":3},{"url":"https://x.com/HegicOptions/status/1896933787923345470","name":"x.com","type":"other","credibility":3}],"severity":"medium"},{"content":"The blockchain investigator ZachXBT has flagged Hegic (old contract) as a notable risk entity within the DeFi ecosystem. ZachXBT is a widely-followed independent on-chain researcher known for documenting exploits, rug pulls, and fraudulent protocols; inclusion on ZachXBT's tracked entities list is treated as an elevated risk signal by the crypto security community. The specific basis for ZachXBT's flag is consistent with the publicly documented incidents: the permanent loss of user funds due to a preventable smart contract defect at launch, the misrepresentation of the pre-launch security review, and the subsequent exploit of a deprecated contract. Community discussion on forums and social media platforms has noted these incidents as cautionary examples of DeFi deployment risk, though most community commentary predates or postdates formal verification and should be treated as low-confidence signals supplementary to the documented primary-source record.","heading":"ZachXBT Flag and Community Signals","sources":[{"url":"https://cryptobriefing.com/defi-bug-freezes-30000-ether-forever/","name":"cryptobriefing.com","type":"other","credibility":3},{"url":"https://decrypt.co/26725/hegic-backpedals-on-typo-claim","name":"decrypt.co","type":"other","credibility":3}],"severity":"medium"}],"timeline":[{"date":"2020-02-20","event":"Hegic protocol announced on EthResearch forum by anonymous developer Molly Wintermute.","source":""},{"date":"2020-04","event":"Trail of Bits conducts a 3-day code review of Hegic, identifying 10 critical flaws and recommending delayed deployment.","source":"","date_original":"2020-04-01"},{"date":"2020-04-23","event":"Hegic v1 deployed to Ethereum mainnet despite Trail of Bits warnings; only a subset of identified critical flaws were patched.","source":""},{"date":"2020-04-24","event":"Critical bug discovered: a missing 's' in the function identifier 'OptionIDs' (should be 'OptionsIDs') permanently locks approximately $28,000–$48,000 in user ETH and DAI. Protocol taken offline.","source":""},{"date":"2020-04-26","event":"Hegic issues public apology retracting the 'typo' characterization and acknowledging a bug. Trail of Bits CEO Dan Guido publicly states the error would have been caught by basic unit testing and that Hegic misrepresented their code review as an 'audit.'","source":""},{"date":"2020-05","event":"New corrected Hegic contract deployed to mainnet. Affected users reimbursed 100% from Wintermute's personal and contributor funds.","source":"","date_original":"2020-05-01"},{"date":"2020-09-09","event":"HEGIC governance token launched on Ethereum via bonding curve.","source":""},{"date":"2020-10","event":"Hegic v888 beta mainnet launched, supporting ETH and WBTC call and put options with staking and liquidity mining.","source":"","date_original":"2020-10-01"},{"date":"2022-01-04","event":"Hegic deploys a WBTC Puts Pool contract (later described as a test/staging contract). The deployer address sends 1.1 WBTC to the contract; the contract is never formally decommissioned.","source":""},{"date":"2022-10","event":"Hegic deploys its current architecture, superseding prior contract versions.","source":"","date_original":"2022-10-01"},{"date":"2025-02-23","event":"Attacker exploits the deprecated January 2022 WBTC Puts Pool contract via the `withdrawWithoutHedge` function, draining 1.1 WBTC (~$80,000). Incident flagged by BlockSec.","source":""},{"date":"2025-02-28","event":"Hegic publishes security report via Discord; confirms current architecture unaffected; announces bug bounty program.","source":""}],"sources_used":[{"url":"https://iq.wiki/wiki/hegic","name":"iq.wiki","type":"other","archive_url":"http://web.archive.org/web/20260217015229/https://iq.wiki/wiki/hegic","credibility":3,"archive_timestamp":"2026-02-17T01:52:29+00:00"},{"url":"https://medium.com/hegic/announcing-hegic-token-liquidity-mining-utilization-rewards-and-staking-d1dd6605f2cd","name":"medium.com","type":"other","archive_url":null,"credibility":3,"archive_error":"error:no-request","archive_status":"unarchivable","archive_timestamp":null},{"url":"https://decrypt.co/35038/hegics-molly-wintermute-im-paying-a-high-price-for-the-mainnet-first-approach-to-building","name":"decrypt.co","type":"other","archive_url":"http://web.archive.org/web/20260416041133/https://decrypt.co/35038/hegics-molly-wintermute-im-paying-a-high-price-for-the-mainnet-first-approach-to-building","credibility":3,"archive_timestamp":"2026-04-16T04:11:33+00:00"},{"url":"https://decrypt.co/26725/hegic-backpedals-on-typo-claim","name":"decrypt.co","type":"other","archive_url":"http://web.archive.org/web/20260207130907/https://decrypt.co/26725/hegic-backpedals-on-typo-claim","credibility":3,"archive_timestamp":"2026-02-07T13:09:07+00:00"},{"url":"https://cryptobriefing.com/defi-bug-freezes-30000-ether-forever/","name":"cryptobriefing.com","type":"other","archive_url":"http://web.archive.org/web/20251209024304/https://cryptobriefing.com/defi-bug-freezes-30000-ether-forever/","credibility":3,"archive_timestamp":"2025-12-09T02:43:04+00:00"},{"url":"https://cryptonews.net/news/security/314071/","name":"cryptonews.net","type":"other","archive_url":"https://web.archive.org/web/20260829113907/https://cryptonews.net/news/security/314071/","credibility":3,"archive_timestamp":"2026-08-29T11:39:07+00:00"},{"url":"https://davidgerard.co.uk/blockchain/2020/04/26/the-dforce-and-hegic-defi-exploits-and-why-smart-contracts-are-bad/","name":"davidgerard.co.uk","type":"other","archive_url":"http://web.archive.org/web/20260512121038/https://davidgerard.co.uk/blockchain/2020/04/26/the-dforce-and-hegic-defi-exploits-and-why-smart-contracts-are-bad/","credibility":3,"archive_timestamp":"2026-05-12T12:10:38+00:00"},{"url":"https://kermankohli.substack.com/p/hegic-vs-trail-of-bits-and-the-issue","name":"kermankohli.substack.com","type":"other","archive_url":"https://web.archive.org/web/20260829115401/https://kermankohli.substack.com/p/hegic-vs-trail-of-bits-and-the-issue","credibility":3,"archive_timestamp":"2026-08-29T11:54:01+00:00"},{"url":"https://www.publish0x.com/interestingcrypto/hegic-case-48-dollars-000-cents-typo-or-why-dofi-protocols-n-xejoomg","name":"publish0x.com","type":"other","archive_url":"http://web.archive.org/web/20251011012202/https://www.publish0x.com/interestingcrypto/hegic-case-48-dollars-000-cents-typo-or-why-dofi-protocols-n-xejoomg","credibility":3,"archive_timestamp":"2025-10-11T01:22:02+00:00"},{"url":"https://blog.verichains.io/p/hegic-options-protocol-how-a-deprecated","name":"blog.verichains.io","type":"other","archive_url":"http://web.archive.org/web/20260608051919/https://blog.verichains.io/p/hegic-options-protocol-how-a-deprecated","credibility":3,"archive_timestamp":"2026-06-08T05:19:19+00:00"},{"url":"https://x.com/HegicOptions/status/1896933787923345470","name":"x.com","type":"other","archive_url":null,"credibility":3,"archive_timestamp":null},{"url":"https://www.nominis.io/insights/crypto-security-incidents-march-2025","name":"nominis.io","type":"other","archive_url":"http://web.archive.org/web/20260417161427/https://www.nominis.io/insights/crypto-security-incidents-march-2025","credibility":3,"archive_timestamp":"2026-04-17T16:14:27+00:00"},{"url":"https://golden.com/wiki/Molly_Wintermute-REPY4D8","name":"golden.com","type":"other","archive_url":null,"credibility":3,"archive_error":"error:no-request","archive_status":"unarchivable","archive_timestamp":null},{"url":"https://github.com/hegic/old-contracts","name":"github.com","type":"other","archive_url":"https://web.archive.org/web/20260829075955/https://github.com/hegic/old-contracts","credibility":3,"archive_timestamp":"2026-08-29T07:59:55+00:00"}],"source_tags":["defillama"],"addresses":[],"reviewed":false,"reviewed_by":null,"model_used":"claude-sonnet-4-6","created_at":"2026-05-04T02:54:25.218978+00:00","updated_at":"2026-08-29T12:34:19.734562+00:00"}}