How to update public information when encountering counterfeit official websites or fake accounts?
This article introduces risk response measures after discovering counterfeit domain names, fake accounts, and fake tokens in Web3 projects, as well as the official information verification and third-party data correction processes.
First handle security risks
When counterfeit domains, fake accounts, or fake tokens are discovered, prioritize publishing verifiable risk alerts on the official website and official social media; submit materials through the reporting mechanism of the respective platform; verify official domain names, contract addresses, and social media entry points. When user funds, phishing, or significant impersonation risks are involved, seek professional support in security and law simultaneously.
Establish a unified official information page
The official website should centrally display official domain names, social media, contract addresses, product entry points, and important announcements. For abandoned domains or accounts, provide migration instructions or risk warnings to reduce the likelihood of users entering incorrect pages from old links.
Update third-party information
When submitting corrections to data platforms or media information pages, provide sources such as official announcements, website screenshots, domain relationships, or social media statements. The purpose of the update is to improve the accuracy of public information, not to determine project ownership or resolve security incidents.
Do not overpromise
Third-party information pages, search engines, and AI products have their own update mechanisms. Project parties can continuously provide clear sources and request corrections, but cannot promise that all erroneous pages will disappear simultaneously.
Next steps
Modify information:
https://www.rootdata.com/projects/submit?ft=modifi
Create project:
https://www.rootdata.com/projects/submit?ft=create
RootData Boost:



