Skip to main content
AVOID.NET
← Berallyreviewed 2026-11-02 · 15 claims checked

Fact-check findings

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

6 claims

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

  1. #4[unverifiable][awaiting moderator]in section: March 2025 Security Incident
    “A day after the incident, Berally announced a token compensation plan of up to 120% for affected holders and claimed to have identified and restricted the attacker through centralized exchange reporting.”
    reviewerBerally announced a token compensation plan of up to 120% and claimed to have identified and restricted the attacker via centralized exchange reportingNeither readable cited source mentions this, and a web search found nothing. Cryptorank was blocked, and the Nominis report was not checked. It may come from a later Berally post.
  2. #5[unverifiable][awaiting moderator]in section: March 2025 Security Incident
    “The attacker exploited residual permissions on the deployer wallet, which had not been revoked after the initial token deployment.”
    reviewerAttacker exploited residual permissions on the deployer wallet not revoked after deploymentNot found in the sources I could read; this is a technical detail asserted as fact.
  3. #8[unverifiable][awaiting moderator]in section: Token Price Collapse and Current Status
    “crashed to an all-time low of approximately $0.0000019 on March 19, 2025 — a decline of roughly 99.7% in approximately five weeks”
    reviewerBRLY all-time low of about $0.0000019 on March 19, 2025, a decline of about 99.7%CoinGecko's data is internally inconsistent, so the ATL and the date could not be verified. Also, $0.0000019 vs $0.000562 is a 99.66% fall, consistent with 99.7%. The summary says about 99% below ATH, which is consistent with CoinGecko's -99.80%.
  4. #12[unverifiable][awaiting moderator]in section: Inside Job Allegations and Community Response
    “These allegations remain unverified and have not been substantiated by any on-chain forensic investigation, law enforcement filing, or credible third-party security firm as of the date of this report.”
    reviewerAllegations have not been substantiated by credible third-party forensic workA negative claim; I found no contradicting forensic report, but the search was limited.
  5. #13[unverifiable][awaiting moderator]in section: Inside Job Allegations and Community Response
    “The ZachXBT flag associated with this entity has been noted, though no specific published ZachXBT investigation or thread directly naming Berally was located in publicly accessible sources at time of writing.”
    reviewerZachXBT flag existsThe page itself says no source was found. A flag with no source is an unsupported implication and could be removed or sourced.
  6. #15[unverifiable][awaiting moderator]in the timeline
    “2025-03-14”
    reviewerTimeline puts the hack on March 14, but Mitrade and Cryptopolitan date Berally's statement March 15March 14 is not found in readable sources; the section says 'approximately March 14-15', which is hedged, but the timeline states March 14 flatly.

stale

1 claim

The claim was accurate when written but events since have overtaken it.

  1. #10[stale][awaiting moderator]in section: Token Price Collapse and Current Status
    “The fully diluted valuation had collapsed to approximately $17,000.”
    reviewerFully diluted valuation collapsed to approximately $17,000Current CoinGecko FDV differs from the page's figure; the original value may be accurate for late May 2025. The correction is low-confidence.
    Proposed correction (not yet applied)
    The fully diluted valuation had collapsed to approximately $17,000 as of late May 2025 (CoinGecko later listed approximately $9,700).

partially supported

3 claims

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

  1. #3[partially supported][awaiting moderator]in the summary
    “and approximately $90,000 drained from the pool”
    reviewerSummary states approximately $90,000 was drained as factThe figure is an unofficial commenter estimate; the summary drops that attribution that the section keeps.
  2. #11[partially supported][awaiting moderator]in section: Token Launch and Tokenomics
    “BRLY reached an all-time high of approximately $0.000562 on February 13, 2025”
    reviewerBRLY reached an ATH of approximately $0.000562 on February 13, 2025Value confirmed; date not shown on the fetched page.
  3. #14[partially supported][awaiting moderator]in the timeline
    “2025-03-16”
    reviewerTimeline entries carry no sourceAll timeline entries have empty source fields. Compensation date (Mar 16) is unverified, and the section text says compensation came 'a day after'.

confirmed

5 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: March 2025 Security Incident
    “'Something from our deployer key on our end was leaked, resulting in all vesting tokens being dumped and drained from the liquidity pool.'”
    reviewerBerally announced the deployer key leak, with vesting tokens dumped and drained from the liquidity poolQuote matches the Cryptopolitan article. Note the cited source for this section is Mitrade, Cryptorank and Nominis, but the quote is verified via Cryptopolitan.
  2. #2[confirmed][no action needed]in section: March 2025 Security Incident
    “Losses were estimated by community members at approximately $90,000.”
    reviewerLosses were approximately $90,000Section text is properly attributed to community members. The summary states it as fact (see next finding).
  3. #6[confirmed][no action needed]in section: Inside Job Allegations and Community Response
    “the Berally X account handler acknowledged fault and described the lapse as a 'skill issue.'”
    reviewerBerally X account called the lapse a 'skill issue' and acknowledged faultMatches the article.
  4. #7[confirmed][no action needed]in section: March 2025 Security Incident
    “Berachain co-founder Smokey posted publicly about potential exploit concerns before Berally's official confirmation.”
    reviewerBerachain co-founder Smokey posted before official confirmationConfirmed.
  5. #9[confirmed][no action needed]in section: Token Price Collapse and Current Status
    “'BRLY tokens have stopped trading on all exchanges listed on CoinGecko,'”
    reviewerCoinGecko reports BRLY has stopped trading on all listed exchangesConfirmed. The page's FDV is $9,704 now versus the $17,000 the page cites, so the FDV figure is stale or has moved.
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.