← Penpie5 decisions on this page
Audit log
Every state-changing event for Penpie: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.
- #1publishby system:backfill2026-05-20 04:21:54ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 420,912,646
- sig
58cjNXUjptDm…M2HsgdeTexplorer ↗- hash
RciYdX1eNXAX…JYRuAqPusha256 → base58
verifying row…full verify ↗canonical bytes (6590 B) ▸
{"actor":"system:backfill","investigation_id":"e5069dd4-353f-4479-86ef-a663685afdb3","kind":"publish","page_slug":"penpie","published_at":"2026-05-20T04:21:54.489Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Penpie","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://docs.magpiexyz.io/the-magpie-ecosystem/penpie-pendle-finance"},{"credibility":3,"name":"","type":"other","url":"https://docs.penpiexyz.io/penpie-ecosystem/introduction"},{"credibility":3,"name":"","type":"other","url":"https://www.auditone.io/blog-posts/the-penpie-hack-understanding-the-september-2024-reentrancy-exploit-and-the-role-of-auditing-in-defi-security"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://www.halborn.com/blog/post/explained-the-penpie-hack-september-2024"},{"credibility":3,"name":"","type":"other","url":"https://threesigma.xyz/blog/exploit/penpie-reentrancy-exploit-analysis"},{"credibility":3,"name":"","type":"other","url":"https://cointelegraph.com/news/penpie-protocol-exploited-suffers-27-million-loss"},{"credibility":3,"name":"","type":"other","url":"https://zokyo.io/blog/penpie-postmortem-analysis-of-the-27m-reentrancy-exploit/"},{"credibility":3,"name":"","type":"other","url":"https://invezz.com/news/2024/09/06/hacker-behind-27m-penpie-heist-applauded-by-euler-exploiter/"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://threesigma.xyz/blog/exploit/penpie-reentrancy-exploit-analysis"},{"credibility":3,"name":"","type":"other","url":"https://cointelegraph.com/news/penpie-protocol-hacker-launders-7m-tornado-cash"},{"credibility":3,"name":"","type":"other","url":"https://dailycoin.com/penpie-hacker-launders-last-batch-of-the-stolen-27m-ether"},{"credibility":3,"name":"","type":"other","url":"https://defi-planet.com/2024/09/penpie-protocol-hacker-reportedly-laundered-7m-through-tornado-cash-within-12-hours-of-27m-theft/"},{"credibility":3,"name":"","type":"other","url":"https://arbiscan.io/tx/0xe44a4e2c1812ff00db4902d61d1bc2815854b38d63e8fe605707614cb1675e79"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://therecord.media/penpie-defi-protocol-ethereum-stolen"},{"credibility":3,"name":"","type":"other","url":"https://thedefiant.io/news/defi/penpie-proposes-compensation-plan-and-insurance-protocol-after-usd27m-exploit"},{"credibility":3,"name":"","type":"other","url":"https://finance.yahoo.com/news/defi-platform-pendle-claims-saved-134115901.html"},{"credibility":3,"name":"","type":"other","url":"https://www.theblock.co/post/314616/pendle-says-it-saved-105-million-that-could-have-been-further-drained-amid-penpie-hack"},{"credibility":3,"name":"","type":"other","url":"https://blog.penpiexyz.io/penpie-post-mortem-report-1ac9863b663a"}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"","type":"other","url":"https://www.auditone.io/blog-posts/the-penpie-hack-understanding-the-september-2024-reentrancy-exploit-and-the-role-of-auditing-in-defi-security"},{"credibility":3,"name":"","type":"other","url":"https://www.quillaudits.com/blog/hack-analysis/penpie-protocol-exploit"},{"credibility":3,"name":"","type":"other","url":"https://medium.com/@Magpieprotocol/magpie-protocol-charting-a-secure-path-following-exploit-c7046d9fc3ca"},{"credibility":3,"name":"","type":"other","url":"https://gov.magpiexyz.io/t/penpie-compensation-plan-draft-02/412"},{"credibility":3,"name":"","type":"other","url":"https://defillama.com/protocol/penpie"}]}],"sources_used":[],"summary":"Penpie is a yield-boosting DeFi protocol built on Pendle Finance by the Magpie DAO ecosystem, allowing users to earn boosted yields on Pendle liquidity pools without directly locking PENDLE tokens. On September 3, 2024, an attacker exploited a reentrancy vulnerability in Penpie's staking contract to drain approximately $27.3 million across Ethereum and Arbitrum, subsequently laundering all stolen funds through Tornado Cash and ignoring recovery appeals. The protocol filed reports with the FBI and Singapore Police but recovered no funds; a partial community compensation plan was proposed but not fully executed.","timeline":[{"date":"2023-05-01","event":"Penpie launches as the first sub-DAO under the Magpie ecosystem, built on Pendle Finance.","source":""},{"date":"2024-05-01","event":"Penpie introduces permissionless pool registration, allowing anyone to create Pendle markets — removing an access control that had previously mitigated reentrancy risk in the batchHarvestMarketRewards() function.","source":""},{"date":"2024-09-03","event":"At 6:23 PM UTC, the reentrancy exploit begins. Three attack transactions drain approximately $27.348 million in wstETH, sUSDe, agETH, and rswETH across Arbitrum and Ethereum.","source":""},{"date":"2024-09-03","event":"Within 20 minutes of the exploit, Pendle Finance pauses all contracts, preventing the attacker from executing a second malicious contract targeting the remaining ~$105 million.","source":""},{"date":"2024-09-03","event":"Penpie team visits Kampong Java Neighbourhood Police Centre in Singapore and files a police report.","source":""},{"date":"2024-09-04","event":"Penpie files a complaint with the FBI's Internet Crime Complaint Center (IC3) and sends an on-chain message to the attacker offering amnesty in exchange for return of funds.","source":""},{"date":"2024-09-04","event":"Attacker begins laundering stolen funds through Tornado Cash; approximately $7 million (26% of total) is laundered within 12 hours of the exploit.","source":""},{"date":"2024-09-06","event":"Euler Finance exploiter sends an on-chain congratulatory message to the Penpie attacker. Penpie offers a 10% bounty for information leading to the attacker's identification.","source":""},{"date":"2024-09-06","event":"Attacker transfers 7,262 ETH ($17.4 million) to an intermediary address; 5,600 ETH is then laundered through Tornado Cash.","source":""},{"date":"2024-09-08","event":"Attacker completes laundering of all remaining stolen ETH through Tornado Cash; full 11,261 ETH balance is confirmed laundered by PeckShield.","source":""},{"date":"2024-10-07","event":"Magpie publishes Penpie compensation plan proposing 27 million Safu Recovery Tokens (SRT) backed by 4% of MGP token supply, and launches Safupie insurance mechanism proposal. Protocol operations resume.","source":""}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision fac17084-a348-45d6-934e-f3f8c5d00894 - #2rescoreby systemsystem2026-10-10 18:49:32ZScore: 10 → 56 (+46)Rescored under Scoring v2, the published formula (avoid.net/scoring): 10 → 56. Problems weighed by who is responsible: incidents the subject suffered −9.6, problems around the subject, caused by others −1.6; legitimacy credit long-running +2.anchoranchored
- chain
- ●mainnet-betaslot 455,369,561
- sig
2dCxknL5Xdjw…4wmJwKa6explorer ↗- hash
F1iLZPVMSpQo…2d6HnbnLsha256 → base58
verifying row…full verify ↗canonical bytes (603 B) ▸
{"actor":"system","decided_at":"2026-10-10T18:49:32.175Z","decision":"rescore","investigation_id":"e5069dd4-353f-4479-86ef-a663685afdb3","new_score":56,"page_slug":"penpie","prev_score":10,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 10 → 56. Problems weighed by who is responsible: incidents the subject suffered −9.6, problems around the subject, caused by others −1.6; legitimacy credit long-running +2.","score_delta":46,"score_model":"v2","sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 83d4b874-482b-4e43-85ad-6e6890d0f112 - #3rescoreby systemsystem2026-11-02 00:04:47ZScore: 56 → 49 (-7)Re-read and rescored after the page was re-researched (2026-11-02). Rescored under Scoring v2, the published formula (avoid.net/scoring): 56 → 49. Problems weighed by who is responsible: incidents the subject suffered −20, concerns that are not fraud −6, problems around the subject, caused by others −1.9; legitimacy credit long-running +2; the penalty for incidents it suffered is capped at 20.anchoranchored
- chain
- ●mainnet-betaslot 464,287,150
- sig
46asfijHVLpa…6yYzUFeBexplorer ↗- hash
8wBdTDpdNdXe…6vbcrqhksha256 → base58
verifying row…full verify ↗canonical bytes (757 B) ▸
{"actor":"system","decided_at":"2026-11-02T00:04:46.604Z","decision":"rescore","investigation_id":"e5069dd4-353f-4479-86ef-a663685afdb3","new_score":49,"page_slug":"penpie","prev_score":56,"reason":"Re-read and rescored after the page was re-researched (2026-11-02). Rescored under Scoring v2, the published formula (avoid.net/scoring): 56 → 49. Problems weighed by who is responsible: incidents the subject suffered −20, concerns that are not fraud −6, problems around the subject, caused by others −1.9; legitimacy credit long-running +2; the penalty for incidents it suffered is capped at 20.","score_delta":-7,"score_model":"v2","sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 79703cad-d623-4a49-9ad6-97b436099e49 - #4reviewby reviewerreviewer2026-11-02 00:06:25ZScore: 49 → 49 (no score change)The core incident narrative (Sept 3, 2024 reentrancy exploit, about $27M, Pendle pause saving about $105M, Singapore and FBI reports) is consistent with sources reached. The compensation section is inconsistent with the cited PIP #15 page: date (Nov 8 vs Oct 7), token name (PRT vs SRT), treasury share (3.5% vs 3%), and Safupie being on hold. One cited CoinTelegraph URL is dead. Current operating status and compensation outcome could not be established.anchoranchored
- chain
- ●mainnet-betaslot 464,287,580
- sig
3VJKivbRuJA7…QRYxyyzoexplorer ↗- hash
AfpkqfEPr6e4…7Z3NUXQusha256 → base58
verifying row…full verify ↗canonical bytes (1299 B) ▸
{"actor":"reviewer","artifact_identity":"f57d70b4533aa5649640707cc24406e2","decided_at":"2026-11-02T00:06:25.413Z","decision":"review","disputed_pct":0.4444,"findings_hash":"RpAwoZANuakayybjU34GA7iprhRgd4JGDCotgoXsRgk","investigation_id":"e5069dd4-353f-4479-86ef-a663685afdb3","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":49,"omissions":{"material":1,"total":1},"page_content_hash":"863af4b95e2918aa0b7e93002b25f78a49c33b82c3e0ea8e33ff328dde1d37e5","page_slug":"penpie","prev_score":49,"reason":"The core incident narrative (Sept 3, 2024 reentrancy exploit, about $27M, Pendle pause saving about $105M, Singapore and FBI reports) is consistent with sources reached. The compensation section is inconsistent with the cited PIP #15 page: date (Nov 8 vs Oct 7), token name (PRT vs SRT), treasury share (3.5% vs 3%), and Safupie being on hold. One cited CoinTelegraph URL is dead. Current operating status and compensation outcome could not be established.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 7e8f016a-39eb-468d-b52d-892e14920c53 - #5review reviseby judgejudge2026-11-02 00:06:25ZScore: 49 → 49 (no score change)Of 9 claim findings, 3 were disputed (claim_findings[0], [1], [2]) and 1 was unverifiable (claim_findings[8]), giving 44% disputed, which falls in the significant band. The disputed items are all in the compensation section: the PIP #15 date (Nov 8, not Oct 7, 2024), the treasury share (3.5%, not 3%) and the token name (PRT, not SRT). The core incident facts (Sept 3, 2024 reentrancy exploit, about $27M, Singapore and FBI reports) were confirmed, and one cited CoinTelegraph URL is dead (claim_findings[7]). The page also presents Safupie as a live proposal when the cited source says it is on hold, and the current status and compensation outcome could not be established (high-priority coverage gap). Reviewer confidence is moderate (0.5), so the penalty sits in the lower half of the band and the page is not delisted.anchoranchored
- chain
- ●mainnet-betaslot 464,287,586
- sig
5r9rnTgM71p9…nvUCmPjwexplorer ↗- hash
Gu634NHXxKXR…XnwpQ1sjsha256 → base58
verifying row…full verify ↗canonical bytes (1832 B) ▸
{"actor":"judge","artifact_identity":"f57d70b4533aa5649640707cc24406e2","band_override":null,"decided_at":"2026-11-02T00:06:25.413Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.4444,"investigation_id":"e5069dd4-353f-4479-86ef-a663685afdb3","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":49,"page_slug":"penpie","prev_score":49,"reason":"Of 9 claim findings, 3 were disputed (claim_findings[0], [1], [2]) and 1 was unverifiable (claim_findings[8]), giving 44% disputed, which falls in the significant band. The disputed items are all in the compensation section: the PIP #15 date (Nov 8, not Oct 7, 2024), the treasury share (3.5%, not 3%) and the token name (PRT, not SRT). The core incident facts (Sept 3, 2024 reentrancy exploit, about $27M, Singapore and FBI reports) were confirmed, and one cited CoinTelegraph URL is dead (claim_findings[7]). The page also presents Safupie as a live proposal when the cited source says it is on hold, and the current status and compensation outcome could not be established (high-priority coverage gap). Reviewer confidence is moderate (0.5), so the penalty sits in the lower half of the band and the page is not delisted.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"severity_override":{"applied":true,"band":"significant","from_band":"significant","reason":"A material omission (Safupie put on hold and plan revised, per the cited PIP #15 page) is not covered on the page, so the verdict is judged by the significant band. This matches the band implied by the claim percentage; it does not make the verdict harsher than that band."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 4a615e58-5479-4860-b2e5-3abee65cbf14
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine —
python -m src.verify_decision <event_id>.