← Port3 Networkreviewed 2026-11-02 · 10 claims checked
Fact-check findings
What an automated fact-checker found when it re-read Port3 Network 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
2 claimsThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #2[disputed][awaiting moderator]in section: November 2025 Security Exploit
“registered themselves as an authorized BridgeIn operator at 20:56:24 UTC on November 23”
reviewerThe attacker registered as BridgeIn operator at 20:56:24 UTC on November 23The page contradicts itself: the timeline and the migration section put the attack and the 20:56 UTC snapshot on Nov 22. Sources I fetched say Nov 22. I could not read a source giving the 20:56:24 timestamp itself.Proposed correction (not yet applied)registered themselves as an authorized BridgeIn operator at 20:56:24 UTC on November 22 - #5[disputed][awaiting moderator]in section: Exchange Delistings and Market Impact
“Kraken listed PORT3 among scheduled December 2025 delistings.”
reviewerKraken listed PORT3 among scheduled December 2025 delistingsThe cited Kraken notice does not include PORT3. Suggest removing the sentence.
unverifiable
4 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #6[unverifiable][awaiting moderator]in the timeline
“Coinone lists PORT3 among scheduled December 2025 delistings.”
reviewerTimeline: Coinone lists PORT3 among scheduled December 2025 delistings on 2025-12-24No source found for a Dec 24 Coinone scheduled-delisting entry. It appears to be a confused version of the Kraken claim, which is itself wrong. The entry has no source. - #8[unverifiable][awaiting moderator]in section: Token Migration and Post-Exploit Recovery
“The BNB Chain migration was finalized on January 31, 2026.”
reviewerBNB Chain migration finalized January 31, 2026 to contract 0xf6402bec...I did not locate a source for the completion date or the contract address. I did not fetch the Coincarp page. - #9[unverifiable][awaiting moderator]in the summary
“ZachXBT has flagged the entity, and the token has been delisted from at least one major exchange (Coinone) following the incident.”
reviewerZachXBT flagged Port3; page itself says it could not verify thisThe summary states the ZachXBT flag as fact, while the section body admits it could not be located. No public source found. The summary overstates relative to the body, and the flag is uncited. - #10[unverifiable][awaiting moderator]in section: ZachXBT Flag and Community Concerns
“ZachXBT, the pseudonymous on-chain investigator known for exposing crypto scams and hacks, has flagged Port3 Network.”
reviewerZachXBT has flagged Port3 Network (section body)Neither cited source (Port3 X post, Medium recap) concerns ZachXBT. No independent confirmation found.
link rot
1 claimA cited source no longer resolves or no longer says what the page attributes to it.
- #4[link rot][awaiting moderator]in section: Exchange Delistings and Market Impact
“https://www.onesafe.io/blog/coinone-port3-delisting-security-breach”
reviewerOnesafe URL cited for the Coinone delisting no longer carries the articleCited URL does not support the claim. The archive link on file points to the blog index, not the article.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #3[partially supported][awaiting moderator]in section: Exchange Delistings and Market Impact
“South Korean exchange Coinone delisted PORT3 on January 26, 2026, citing unresolved security concerns stemming from the hack.”
reviewerCoinone delisted PORT3 on January 26, 2026 (summary and section)Date and cause corroborated by secondary reports found via search. The cited onesafe URL does not support it, and I did not read Coinone's own notice.
confirmed
2 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in the summary
“In November 2025 the project suffered a critical exploit in which an attacker leveraged a boundary-condition vulnerability in the third-party CATERC20 cross-chain standard to mint approximately 1 billion unauthorized PORT3 tokens valued at roughly $13 million, triggering an 80% token price collapse and full contract migration.”
reviewerExploit minted about 1 billion PORT3 tokens, about $13M, 80% price collapse, via CATERC20 vulnerabilityCore exploit facts are corroborated. The $13M figure is the nominal value of the minted supply; realized proceeds were about $166K, which the page states in the body. - #7[confirmed][no action needed]in section: Token Migration and Post-Exploit Recovery
“In addition, 162.75 million team-allocated tokens were burned to offset the unauthorized minting by the attacker.”
reviewer162.75 million team tokens were burned and 1:1 migration on BNB Chain with snapshot at 20:56 UTCBurn, 1:1 ratio, snapshot time and compensation of 200-500 tokens are corroborated by OKX and TechFlow summaries. The 'team-allocated' detail was not confirmed in what I read.
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.