Skip to main content
AVOID.NET
← Penpiereviewed 2026-11-02 · 9 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Penpie against the sources the page cites. Only the most recent review is shown.

Read this first

These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.

“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.

Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.

disputed

3 claims

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

  1. #1[disputed][awaiting moderator]in section: Team response and law enforcement
    “On October 7, 2024, Magpie XYZ published a compensation plan for affected users (PIP #15), following an earlier draft.”
    reviewerMagpie published its compensation plan (PIP #15) on October 7, 2024The cited official forum post is dated November 8, 2024, not October 7.
    Proposed correction (not yet applied)
    On November 8, 2024, Magpie XYZ published a compensation plan for affected users (PIP #15), following an earlier draft.
  2. #2[disputed][awaiting moderator]in the timeline
    “2024-10”
    reviewerTimeline date for PIP #15 publicationSame date error as in the section text. The 'resumed operations in October 2024' part of this entry was not checked separately.
    Proposed correction (not yet applied)
    2024-11
  3. #3[disputed][awaiting moderator]in section: Team response and law enforcement
    “backed by 4% of MGP token supply (1% from the team allocation and 3% from the treasury)”
    reviewerPIP #15 backed by 4% of MGP supply (1% team + 3% treasury) via Safu Recovery TokensCited PIP #15 gives 3.5% from treasury and names the token PRT. The page's SRT and 3% figures may come from an earlier draft. The token name 'Safu Recovery Tokens' elsewhere in the section and timeline needs the same check.
    Proposed correction (not yet applied)
    backed by 4.5% of MGP token supply (1% from the team allocation and 3.5% from the treasury)

unverifiable

1 claim

No source the reviewer could reach confirms or contradicts the claim.

  1. #9[unverifiable][awaiting moderator]in section: Pendle Finance involvement and the $105M at risk
    “No arrest or attribution had been publicly confirmed as of mid-2026.”
    reviewerNo arrest or attribution publicly confirmed as of mid-2026Absence of reports is consistent with the claim, but a negative cannot be proven from the cited 2024 sources.

partially supported

2 claims

The cited evidence supports part of the claim but not all of it.

  1. #4[partially supported][awaiting moderator]in section: Team response and law enforcement
    “It also earmarked 20% of Penpie's vePENDLE revenue and 20% of Magpie's overall monthly revenue for open-market SRT buybacks, and proposed Safupie, a new sub-DAO acting as a decentralized insurance fund that would take premiums from Magpie's sub-DAOs and pay compensation for future exploits in the ecosystem.”
    reviewerSafupie was proposed as a new insurance sub-DAO and the plan buys back SRT with 20% of Magpie overall monthly revenueRevenue source differs (vlMGP revenue vs overall monthly revenue) and Safupie is on hold in PIP #15. No clean substring correction offered because the plan version in question is unclear.
  2. #7[partially supported][awaiting moderator]in the timeline
    “AstraSec audits the new registration contracts in isolation; PendleStakingBaseUpg is excluded from scope.”
    reviewerAstraSec audited only the new registration contracts, excluding PendleStakingBaseUpgSnippet supports the scope limitation. The explicit exclusion of PendleStakingBaseUpg was not directly seen.

confirmed

2 claims

The cited evidence supports the claim as written.

  1. #5[confirmed][no action needed]in section: Pendle Finance involvement and the $105M at risk
    “On September 3, 2024, team members filed a police report at the Kampong Java Neighbourhood Police Centre in Singapore, and on September 4, 2024, Penpie filed a complaint with the FBI's Internet Crime Complaint Center (IC3).”
    reviewerSingapore police report on Sept 3 and FBI IC3 complaint on Sept 4, 2024; VPN IP passed to Singapore investigatorWeekdays in the source map to the stated dates.
  2. #6[confirmed][no action needed]in section: September 3, 2024 exploit
    “On September 3, 2024, an attacker exploited a reentrancy vulnerability in Penpie's PendleStakingBaseUpg::batchHarvestMarketRewards() function on Arbitrum and Ethereum.”
    reviewerExploit of about $27M on Sept 3, 2024; 11,113.6 ETH; Pendle paused contracts protecting about $105MCore incident facts (date, $27M, reentrancy, Pendle pause saving about $105M, 11,113.6 ETH) agree with the sources I reached. Detailed on-chain addresses and hashes were not individually verified.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.