0x0da55ac10da5…0da55abe
Binance Rejects ShinyHunters’ Claim of 335.9 Million User Records
Binance founder CZ rejected ShinyHunters’ claim that it stole about 335.9 million user records. The group demanded $900,000, but the alleged cache and any breach remain unverified.

Outputs
CZ rejected ShinyHunters’ claim of about 335.9 million stolen Binance user records.
ShinyHunters demanded $900,000 for the alleged data cache.
The claimed cache included KYC files, passwords, contact details and wallet private keys.
Binance found no indication that its systems were breached.
The review did not establish whether the advertised records were genuine.
Binance founder CZ rejected ShinyHunters’ claim that the exchange lost about 335.9 million user records, calling it false or a scam while the purported leak remains unverified. ShinyHunters separately demanded $900,000 for the alleged cache.
What did ShinyHunters say it took?
ShinyHunters said its alleged cache covered a wide range of Binance customer information. The group identified these records:
- Know-your-customer (KYC) files
- Account passwords
- Email addresses and phone numbers
- Wallet private keys
The demand put a specific price on the claim: $900,000. ShinyHunters presented the material as data it had stolen from Binance.
Each category touches a different operating layer. Passwords affect account access. KYC files affect identity checks and compliance review. Wallet private keys affect control of funds. If the material proved genuine, the breach would touch account access, identity verification and customer support at the same time, with consequences beyond any routine exchange incident.
ShinyHunters’ description establishes what the group says it possesses. It does not establish how the group obtained the material, whether the files are authentic or whether the claimed volume is accurate.
Why did CZ reject the claim?
CZ’s rejection focused partly on what wallet private keys would make possible. He said: “move funds directly instead of trying to sell the information.” A seller demanding $900,000 could seek payment for information rather than exercise control over users’ funds.
The logic puts the seller’s claimed incentive in plain view. A working set of private keys would offer direct control of customer assets, not merely details about them, making the proposed $900,000 information sale a questionable operational choice.
That argument challenges the claim’s operational logic. It does not, by itself, authenticate or disprove every advertised record.
CZ said he had noticed the allegation the previous day. He initially thought its false nature would be obvious. The claim nevertheless continued to appear in headlines.
The persistence kept the allegation visible even after Binance rejected it. Headlines extended the life of the demand despite Binance’s private assessment.
What did Binance’s review establish?
Binance had previously described the listing as likely a scam after reviewing its terms and sample material. In its earlier response, the exchange said it found “no indication that its systems were breached.”
The assessment did not establish whether the advertised records were genuine. That distinction matters.
Authenticating the cache requires evidence that the data exists, came from Binance and matches the claimed scale, rather than merely evidence that the listing looks fraudulent.
An intrusion review looks for signs of compromise in Binance systems. That differs from proving that every advertised record exists and belongs to the claimed 335.9 million-record cache.
The review therefore supports a narrow statement: Binance found no indication of a systems breach. It does not support a broader conclusion that the advertised records cannot exist.
ShinyHunters’ 335.9-million-record claim therefore remains unverified. Its $900,000 asking price states a commercial term. It does not prove ownership, provenance or authenticity.
What does this change for Binance and users?
For Binance, the immediate issue is not a proven breach. It is an unverified claim at enormous scale.
A false listing can still generate support demand and keep customer questions active, while a genuine cache would require account-access, identity-verification and fund-security responses.
For users, the practical answer is narrow: the claim alone identifies no confirmed affected account and establishes neither a completed breach nor a safe all-clear.
Until independent authentication verifies the records, the supportable conclusion is that an alleged cache exists, not that the group took 335.9 million records. The $900,000 demand does not fill that evidentiary gap.
Binance and ShinyHunters have disclosed no verification deadline or enforcement timetable. The next meaningful checkpoint is independent authentication of the claimed records or a documented breach.
via tokenpost.com (Source)
More from Marcus Bennett
Show full bio
Senior reporter covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
952 articles