Skip to main content
AVOID.NET
← Zohar Pinhasi / MonsterCloudreviewed 2026-10-27 · 16 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Zohar Pinhasi / MonsterCloud 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 2partially supported 5confirmed 92 corrections pending · 0 applied

disputed

2 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. #9[disputed][awaiting moderator]in section: Background: Zohar Pinhasi and MonsterCloud
    “The company listed former TSA Deputy Director John Pistole as the sole member of a 'Cyber Security Advisory Council,'”
    reviewerPistole's title: former TSA Deputy DirectorProPublica calls him a former FBI deputy director. He later led the TSA as Administrator, not Deputy Director, so the page's title is wrong.
    Proposed correction (not yet applied)
    The company listed former FBI Deputy Director John Pistole as the sole member of a 'Cyber Security Advisory Council,'
  2. #10[disputed][awaiting moderator]in the timeline
    “2019-05-16”
    reviewerProPublica published its piece on May 16, 2019ProPublica's page shows May 15, 2019. A May 16 date may reflect a later republication, so confidence is moderate.
    Proposed correction (not yet applied)
    2019-05-15

partially supported

5 claims

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

  1. #3[partially supported][awaiting moderator]in section: Criminal Charges (October 2026)
    “The DOJ press release quoted U.S. Attorney Joseph Nocella Jr. as stating that Pinhasi 're-victimized his clients while extracting hefty profit,' and FBI Assistant Director James C. Barnacle Jr. as stating he 'turned the victim's crisis into his own profit center.'”
    reviewerDOJ press release quoted Nocella and Barnacle with the stated phrasesNocella's 're-victimized his clients' is real, but the rest of that quote and Barnacle's 'profit center' quote were not found in any fetched source. They may come from the full release or be misquoted. I did not propose a replacement because I could not read the full text.
  2. #4[partially supported][awaiting moderator]in section: Criminal Charges (October 2026)
    “but no co-defendants have been publicly named.”
    reviewerUnnamed co-conspirators quoted as 'individuals whose identities are both known and unknown to the Grand Jury, including MonsterCloud employees and contractors'No co-defendants named is supported. The quoted indictment language was not seen in the sources I fetched.
  3. #11[partially supported][awaiting moderator]in section: Prior Investigative Reporting (2019)
    “include the Trumann, Arkansas Police Department (November 2018, Dharma ransomware), the Lamar County, Texas Sheriff's Office (May 2018), and the Lauderdale County, Mississippi Sheriff's Office (May 2018).”
    reviewerProPublica: Trumann AR PD (Nov 2018, Dharma), Lamar County TX and Lauderdale County MS (May 2018); officials believed no ransom paidThe agencies and months are right. The November 2018 year is not stated in my fetch (Dharma, a 2018 timeframe is plausible). Lamar County's belief that no ransom was paid fits ProPublica; I did not confirm it for Lauderdale.
  4. #13[partially supported][awaiting moderator]in section: Background: Zohar Pinhasi and MonsterCloud
    “at least one client of that earlier firm alleged, in ProPublica's 2019 reporting, that Pinhasi demanded additional payment and disappeared after a data loss incident”
    reviewerA PC USA client alleged Pinhasi demanded additional payment and disappeared after data lossA PC USA client complaint exists, but my read does not match the 'demanded payment and disappeared' detail. The 'Pinhasi disputed' framing is also not seen.
  5. #15[partially supported][awaiting moderator]in section: Background: Zohar Pinhasi and MonsterCloud
    “Zohar Pinhasi, 50, is a dual U.S.-Israeli national who resided in Hollywood, Florida at the time of his indictment.”
    reviewerPinhasi is 50, dual U.S.-Israeli nationalAge and nationality confirmed; Hollywood, Florida is not stated in the sources I read (ProPublica placed the storefront there).

confirmed

9 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: Criminal Charges (October 2026)
    “Pinhasi was arraigned on October 7, 2026 in federal court in Brooklyn, where he pleaded not guilty and was released on a $2 million bond.”
    reviewerCharges: two counts wire fraud and one count wire fraud conspiracy; arraigned Oct 7, 2026 in Brooklyn; not guilty; $2M bondCounts, arraignment, plea and bond confirmed by DOJ and CyberScoop. Indictment date Sept 23, 2026 matches the label in CyberScoop's indictment file.
  2. #2[confirmed][no action needed]in section: Criminal Charges (October 2026)
    “he faces a maximum sentence of 20 years in prison per count”
    reviewerMaximum sentence is 20 years per countConsistent with DOJ.
  3. #5[confirmed][no action needed]in section: Financial Allegations: Scale and Markup
    “Pinhasi allegedly billed clients over $19 million in total while paying ransomware operators over $8 million, yielding an alleged markup of approximately $11 million.”
    reviewerOver $19M collected, over $8M paid in ransom, about $11M markupTotals confirmed; $11M is simple subtraction.
  4. #6[confirmed][no action needed]in section: Financial Allegations: Scale and Markup
    “in August 2023, Pinhasi paid a ransomware affiliate approximately $8,200 to obtain a decryption key but charged the client approximately $150,000”
    reviewerAugust 2023: about $8,200 ransom vs about $150,000 chargedConfirmed; the roughly 1,730 percent figure is the outlet's or the page's own arithmetic and is correct.
  5. #7[confirmed][no action needed]in section: Financial Allegations: Scale and Markup
    “in October 2021, he allegedly paid approximately $236,000 in ransom while charging a customer approximately $380,000”
    reviewerOctober 2021: about $236,000 ransom vs about $380,000 chargedSupported by The Hacker News. Not in the DOJ release or SecurityWeek, and the page attributes it to 'the government's charging documents', which only that one outlet backs.
  6. #8[confirmed][no action needed]in the summary
    “The alleged scheme ran from approximately June 2018 to June 2023.”
    reviewerScheme ran June 2018 to June 2023Matches secondary reporting; the DOJ text I could read did not state the period explicitly.
  7. #12[confirmed][no action needed]in section: Prior Investigative Reporting (2019)
    “Pinhasi acknowledged the use of aliases to ProPublica, stating: 'We go based on aliases, because we're dealing with cyberterrorists.'”
    reviewerIncorporated in Florida 2013; Pinhasi claims to have led since 2003; alias remarkConfirmed. I did not verify the fabricated Google reviews or Israeli military claims in the ProPublica text I read.
  8. #14[confirmed][no action needed]in section: Background: Zohar Pinhasi and MonsterCloud
    “approximately 20 employees and handled an estimated 30 client calls per day”
    reviewerApproximately 20 employees and about 30 client calls per dayProPublica says 'up to 30' calls; 'an estimated 30' is a mild overstatement.
  9. #16[confirmed][no action needed]in section: Case Status and Pending Proceedings
    “No trial date has been publicly announced.”
    reviewerNo trial date has been publicly announcedTrue as stated, but the page omits the reported plea negotiations (see omissions).
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.