Fact-check findings
What an automated fact-checker found when it re-read Polycule against the sources the page cites. Only the most recent review is shown.
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
1 claimThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #1[disputed][awaiting moderator]in the summary
“ZachXBT has flagged the entity in connection with these concerns.”
reviewerZachXBT has flagged the entity in connection with rug pull concernsNo source found linking ZachXBT to Polycule. Section 4 concedes this is unconfirmed, so the summary states it more strongly than the body.Proposed correction (not yet applied)Rug pull allegations were raised publicly by Ryan Chi of Insiders.bot and covered by crypto media.
unverifiable
2 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #2[unverifiable][awaiting moderator]in the timeline
“ZachXBT flagged in connection with the entity.”
reviewerZachXBT flagged in connection with the entity (timeline)No evidence found of ZachXBT involvement. The timeline entry has no source. - #7[unverifiable][awaiting moderator]in section: Structural Security Risks in Custodial Bot Architecture
“PCULE was reported down 4.48% and POLY (a related token) down 1.13% in immediate post-incident trading.”
reviewerPCULE down 4.48% after the hackFigure not reproduced. It comes from a volatile price widget and is low-value.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #6[partially supported][awaiting moderator]in section: Structural Security Risks in Custodial Bot Architecture
“briefly pushing the market cap to approximately $57 million USD”
reviewerToken peaked at $57M market cap after rebrandInternally inconsistent: section 0 says the peak was about $15M and the rebrand reached $22.8M, while this section says $57M. Phemex supports $22.8M only. I did not find a source for $57M.
confirmed
4 claimsThe cited evidence supports the claim as written.
- #3[confirmed][no action needed]in section: Project Overview
“This pivot saw the token surge approximately 44% within 24 hours, reaching a market cap of $22.8 million.”
reviewerToken surged about 44% to a $22.8M market cap after the PMX rebrand on Oct 1, 2025 with MeteoraMatches the Phemex article. - #4[confirmed][no action needed]in section: Funding and Backers
“On June 8, 2025, Polycule announced it had secured a $560,000 seed investment from AllianceDAO”
reviewerAllianceDAO $560,000 seed announced June 8, 2025Supported. - #5[confirmed][no action needed]in section: January 2026 Security Incident
“with approximately $230,000 in user funds stolen”
reviewerBot compromised, about $230,000 stolen, Jan 7-8 2026Amount and 'first known case' quote are confirmed. The Phemex article does not mention SSRF. That detail rests on other cited sources, which I did not fetch. - #8[confirmed][no action needed]in section: Rug Pull Allegations and Community Response
“Following the January 8, 2026 announcement, the Polycule team went silent.”
reviewerTeam silent after Jan 8; withdrawals frozen by Jan 12; rivals alleged rug pullConsistent with search snippets. Each cited article was not individually fetched. The mexc.com/news/460576 source is marked gone by the archiver.