Skip to main content
AVOID.NET
← OpenClaw GitHub Phishing Campaignreviewed 2026-10-28 · 22 claims checked

Fact-check findings

What an automated fact-checker found when it re-read OpenClaw GitHub Phishing Campaign 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 4confirmed 150 corrections pending · 0 applied

unverifiable

3 claims

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

  1. #11[unverifiable][awaiting moderator]in section: Wallet Drainer Infrastructure
    “The malware enumerated more than 90 cryptocurrency wallet addresses and over 100 blockchain RPC endpoints for target reconnaissance.”
    reviewerThe malware enumerated more than 90 cryptocurrency wallet addresses and over 100 blockchain RPC endpoints for target reconnaissance.The only source for this specific technical detail is the OX Security blog, which could not be fetched (403 bot wall) through any available route. No secondary source corroborates these specific figures.
  2. #14[unverifiable][awaiting moderator]in section: Victim Impact and Confirmed Losses
    “Moshe Siman Tov Bustan of OX Security said: 'During our analysis, we found only one address belonging to the threat actor, which hadn't sent or received any funds yet.'”
    reviewerMoshe Siman Tov Bustan of OX Security said: 'During our analysis, we found only one address belonging to the threat actor, which hadn't sent or received any funds yet.'Bustan is a real OX Security researcher (confirmed via his OX author page and conference bios), and the substance matches OX's reported 'no confirmed victims' finding, but the exact quote could not be verified because the only likely source is blocked.
  3. #16[unverifiable][awaiting moderator]in section: Victim Impact and Confirmed Losses
    “One aggregator (ainvest.com) alleged a $30 million drain figure in connection with the March 2026 campaign, but the figure is not corroborated by OX Security, Decrypt, CoinDesk or CSO Online and should be treated as low-confidence.”
    reviewerOne aggregator (ainvest.com) alleged a $30 million drain figure in connection with the March 2026 campaign, not corroborated by OX Security, Decrypt, CoinDesk or CSO Online.Could not independently confirm ainvest.com published this figure, but no search turned up a $30M loss figure anywhere, consistent with the page's own characterization of it as low-confidence and uncorroborated. The page's hedge, if the underlying claim exists, is itself defensible.

partially supported

4 claims

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

  1. #7[partially supported][awaiting moderator]in section: January 2026 Wave: Account Hijacking and the CLAWD Token
    “and he was quoted as saying: 'I didn't know that they're not just good at harassment, they are also really good at using scripts and tools.'”
    reviewerSteinberger was quoted as saying: 'I didn't know that they're not just good at harassment, they are also really good at using scripts and tools.'The substance is corroborated by an independent report of the same Lex Fridman interview, but none of the section's seven cited sources actually contains this quote, and the exact wording could not be verified against a primary transcript. This is a sourcing gap: the quote's real source (Lex Fridman Podcast #491) is never cited anywhere on the page.
  2. #15[partially supported][awaiting moderator]in section: Victim Impact and Confirmed Losses
    “A Hacker News thread from the same period collected reports from more than ten GitHub users who said they had received the same or similar airdrop message, several noting that the sending accounts were newly created; these are self-reported, unverified community accounts of receiving the lure, not confirmed losses.”
    reviewerA Hacker News thread collected reports from more than ten GitHub users who said they had received the same or similar airdrop message, several noting the sending accounts were newly created.The page's own cited source does not support the specific counts given; it overstates both the number of reporters and the number who flagged new account age. The core point (self-reported, unverified, no losses) is accurate.
  3. #21[partially supported][awaiting moderator]in the timeline
    “2026”
    reviewerThe trademark claim/rebrand and the CLAWD account hijacking both occurred in January 2026 (timeline dated only to year 2026).Not wrong, but needlessly imprecise given the cited source supports month-level precision; the event text itself already says 'reported as January 2026.'
  4. #22[partially supported][awaiting moderator]in the timeline
    “2026”
    reviewerScammers seized OpenClaw's old GitHub and X accounts and promoted the fraudulent $CLAWD token during the January 2026 handle transition.Same imprecision issue as timeline[0]; both describe events reliably dated to January 2026 but store only the bare year.

confirmed

15 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in the summary
    “In January 2026, scammers hijacked the project's old GitHub and X handles during a forced rebrand to promote a fake CLAWD token on Solana that reached about $16 million in market capitalization before collapsing more than 90%”
    reviewerScammers hijacked OpenClaw's old GitHub and X handles in January 2026 during a forced rebrand and used them to promote a fake CLAWD token on Solana that reached about $16 million market cap before collapsing more than 90%.Corroborated by multiple independent outlets and directly by a live-fetched article (Yellow.com) using nearly identical language.
  2. #2[confirmed][no action needed]in the summary
    “in March 2026, throwaway GitHub accounts tagged developers with fake $5,000 CLAW token airdrops leading to token-claw[.]xyz, a cloned site running an obfuscated wallet drainer.”
    reviewerIn March 2026, throwaway GitHub accounts tagged developers with fake $5,000 CLAW token airdrops leading to token-claw[.]xyz, a cloned site running an obfuscated wallet drainer.Well corroborated across OX Security and multiple outlets.
  3. #3[confirmed][no action needed]in the summary
    “OX Security, which disclosed the March wave, found no confirmed drainer victims at the time, and no later wave has been verified.”
    reviewerOX Security, which disclosed the March wave, found no confirmed drainer victims at the time, and no later wave has been verified.Independently re-searched for any later wave through October 2026; found none.
  4. #4[confirmed][no action needed]in section: Campaign Overview
    “OpenClaw passed 300,000 GitHub stars after Steinberger was appointed to lead personal AI agent development at OpenAI, becoming one of GitHub's most-starred repositories in 2026, which made its developer community a high-value target.”
    reviewerOpenClaw passed 300,000 GitHub stars after Steinberger was appointed to lead personal AI agent development at OpenAI, becoming one of GitHub's most-starred repositories in 2026.No primary GitHub source was checked directly, but secondary star-trackers consistently show the repository crossing 300K stars within weeks of the OpenAI appointment. Note the page is actually conservative: several sources describe OpenClaw as having overtaken React to become THE single most-starred repository, not merely 'one of' the most-starred.
  5. #5[confirmed][no action needed]in section: January 2026 Wave: Account Hijacking and the CLAWD Token
    “In January 2026, Steinberger began a forced rebrand after Anthropic raised a trademark claim over the similarity between 'Clawd' and 'Claude.'”
    reviewerSteinberger began a forced rebrand after Anthropic raised a trademark claim over the similarity between 'Clawd' and 'Claude.'Confirmed. Page omits that the project briefly used an intermediate name, 'Moltbot,' for about two days before settling on OpenClaw — noted separately as a minor omission, not a factual error.
  6. #6[confirmed][no action needed]in section: January 2026 Wave: Account Hijacking and the CLAWD Token
    “writing: 'I will never do a coin. Any project that lists me as coin owner is a SCAM.'”
    reviewerSteinberger wrote: 'I will never do a coin. Any project that lists me as coin owner is a SCAM.'Verbatim quote confirmed against the cited source.
  7. #8[confirmed][no action needed]in section: March 2026 Wave: GitHub Issue Tagging and Fake CLAW Airdrop
    “The lure read: 'Appreciate for your contributions on GitHub. We analyzed profiles and chose developers to get OpenClaw allocation,' and promised about $5,000 in CLAW tokens.”
    reviewerThe lure read: 'Appreciate for your contributions on GitHub. We analyzed profiles and chose developers to get OpenClaw allocation,' and promised about $5,000 in CLAW tokens.Verbatim match confirmed, and independently corroborated in GitHub issue #49836 comments.
  8. #9[confirmed][no action needed]in section: March 2026 Wave: GitHub Issue Tagging and Fake CLAW Airdrop
    “Pages differ on the dates: one dates account creation to March 11 and the launch and public disclosure to March 18, 2026; another dates account creation, tagging and account deletion to March 12 and OX Security's first disclosure to March 19, 2026.”
    reviewerPages differ on the dates of account creation, campaign launch and disclosure (March 11/18 vs March 12/19, 2026).This genuinely reflects real disagreement in the underlying reporting rather than a factual error; the page's hedge is accurate.
  9. #10[confirmed][no action needed]in section: Wallet Drainer Infrastructure
    “After deobfuscation, researchers identified three C2 commands, PromptTx, Approved and Declined, used to prompt and monitor malicious approval transactions in real time while relaying the wallet address, transaction value and username to the C2 server in encoded form.”
    reviewerAfter deobfuscation, researchers identified three C2 commands — PromptTx, Approved and Declined — used to relay wallet address, transaction value and username to the C2 server.Confirmed via a reachable secondary source since the primary OX Security blog returned HTTP 403 to automated fetches.
  10. #12[confirmed][no action needed]in section: Wallet Drainer Infrastructure
    “OX Security attributed the Ethereum address 0x6981E9EA7023a8407E4B08ad97f186A5CBDaFCf5 to the threat actor; it showed no transactions at the time of disclosure.”
    reviewerOX Security attributed the Ethereum address 0x6981E9EA7023a8407E4B08ad97f186A5CBDaFCf5 to the threat actor; it showed no transactions at the time of disclosure.Address attribution is well corroborated; the specific 'no transactions' detail rests on the blocked primary source but is consistent with every secondary source's 'no confirmed victims' framing.
  11. #13[confirmed][no action needed]in section: OpenClaw Project Response
    “Community members filed a GitHub security issue (#49836) in the OpenClaw repository.”
    reviewerCommunity members filed a GitHub security issue (#49836) in the OpenClaw repository.Directly verified against GitHub. Note this issue was opened March 18, 2026, one day before the March 19 date under which the parallel timeline entry (timeline[7]) bundles it.
  12. #17[confirmed][no action needed]in section: OpenClaw Project Response
    “In February 2026, after the CLAWD incident, he imposed a blanket ban on cryptocurrency discussion in OpenClaw's official Discord server, including the words 'bitcoin' and 'crypto,' describing the project as 'open source and non-commercial' and saying it would never conduct token distributions.”
    reviewerAfter the CLAWD incident, Steinberger imposed a blanket ban on cryptocurrency discussion in OpenClaw's Discord, including the words 'bitcoin' and 'crypto.'Confirmed via live fetch of a corroborating source; CoinDesk's own Feb 22, 2026 headline matches this directly.
  13. #18[confirmed][no action needed]in section: OpenClaw Project Response
    “After the March 2026 disclosure, Steinberger again warned publicly that any crypto-themed outreach invoking the OpenClaw name should be treated as fraudulent and that the project has no token and never will, saying: 'We would never do that.'”
    reviewerAfter the March 2026 disclosure, Steinberger again warned that any crypto-themed outreach invoking the OpenClaw name should be treated as fraudulent, saying: 'We would never do that.'Confirmed via an independent outlet quoting the same statement, since the cited BeInCrypto source itself could not be fetched.
  14. #19[confirmed][no action needed]in section: Status After the March 2026 Disclosure
    “a community tracker (joylarkin/openclaw-security-news) lists headlines through at least July 20, 2026 about the project's software vulnerabilities”
    reviewerA community tracker (joylarkin/openclaw-security-news) lists headlines through at least July 20, 2026 about the project's software vulnerabilities.Precisely confirmed against the live tracker.
  15. #20[confirmed][no action needed]in section: Status After the March 2026 Disclosure
    “A later review covering the period through September 2026 found no court filing, regulatory advisory, security-vendor writeup or mainstream report documenting a distinct new wave of the CLAW-token airdrop drainer, new confirmed victims, new phishing domains or new tactics after the original March 2026 disclosure.”
    reviewerA later review covering the period through September 2026 found no distinct new wave of the CLAW-token airdrop drainer, new confirmed victims, new phishing domains or new tactics after the original March 2026 disclosure.Independent searching corroborated this; the only post-March OpenClaw-branded security incidents found (e.g., an 'OpenClaw Deployer' trojanized repo, malicious npm packages) are a different attack type (infostealer/RAT supply-chain malware, not the CLAW wallet-drainer), which the claim's careful scoping ('CLAW-token airdrop drainer') correctly excludes. See omission_findings for whether readers should be told about those adjacent campaigns.
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.