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

Fact-check findings

What an automated fact-checker found when it re-read PrismaLST 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.

unverifiable 3partially supported 2confirmed 40 corrections pending · 0 applied

unverifiable

3 claims

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

  1. #4[unverifiable][awaiting moderator]in section: The Exploit
    “By directly invoking mkUSD.flashLoan() with 1,442,100 mkUSD”
    reviewerPrimary attacker flash-loaned 1,442,100 mkUSDAmount not in the post-mortem; CertiK/ImmuneBytes were not checked in this pass.
  2. #8[unverifiable][awaiting moderator]in section: Recovery Controversy
    “A DAO governance vote resulted in 100% approval to resume operations”
    reviewerProtocol resumed operations around April 6, 2024 after a DAO vote of 100% approvalRestart vote surfaced in search results but the article body was not fetched; the 100% figure and dates were not checked.
  3. #9[unverifiable][awaiting moderator]in section: On-Chain Evidence
    “who reportedly initiated legal proceedings in Vietnam and Australia”
    reviewerZachXBT allegations about the attacker's links and legal proceedingsNot fetched. The page already hedges with 'reportedly' and 'alleged'.

partially supported

2 claims

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

  1. #6[partially supported][awaiting moderator]in section: On-Chain Evidence
    “approximately 1,850 ETH (roughly $6.5 million) was subsequently routed through Tornado Cash”
    reviewerAbout 1,850 ETH (~$6.5M) routed through Tornado CashCited source says 1,840 ETH; 1,850 may come from a later count. Immaterial difference.
  2. #7[partially supported][awaiting moderator]in the summary
    “from a pre-exploit peak of approximately $220 million to under $300K”
    reviewerTVL collapsed from a pre-exploit peak of about $220M to under $300KOne secondary source puts the all-time peak near $500M, so calling $220M the 'peak' is doubtful; $220M may be the TVL just before the exploit. The sub-$300K current figure could not be verified because DeFiLlama blocked the fetch.

confirmed

4 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: The Exploit
    “On March 28, 2024, at approximately 11:25 UTC, Prisma Finance was exploited through a critical vulnerability in its MigrateTroveZap contract”
    reviewerExploit began 11:25 UTC on March 28, 2024 via MigrateTroveZap; primary attacker EOA 0x7E39...4202Time, address and contract match the official post-mortem.
  2. #2[confirmed][no action needed]in section: The Exploit
    “The emergency multisig paused the protocol at 12:51 UTC, roughly 90 minutes after the initial transaction.”
    reviewerEmergency multisig paused protocol at 12:51 UTCConfirmed.
  3. #3[confirmed][no action needed]in section: The Exploit
    “The total loss across all three exploiters was approximately 3,479 ETH, or about $12.3 million at the time.”
    reviewerTotal loss about 3,479 ETH / $12.3METH figure exact; USD value approximate ($12M in post-mortem, $12.3M elsewhere).
  4. #5[confirmed][no action needed]in section: The Exploit
    “Two copycat attackers replicated the technique, together accounting for approximately an additional $700,000 in losses.”
    reviewerCopycats accounted for about $700,000 additional lossesConsistent with the difference between total and primary share.
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.