Handle reuse across failed/rugged projects
Babylon Protocol's assessment for RD-F-118 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Primary X/Twitter handle @babylonlabs_io confirmed active. January 2025 phishing compromise was an external attack (not handle reuse from a rugged project); account recovered within 6 hours, $0 loss. Handle @babylonlabs_io has no documented prior association with a rugged or failed project. David Tse's personal handle and Fisher Yu's (@DrFisherYu) show no prior rug-associated handle recycling. GitHub org babylonlabs-io: no prior rug-associated name found.
Sources #
- URL
- Babylon Labs X Account Phishing Case StudyX account phishing case — confirms external attack not handle reuseretrieved 2026-05-04
Methodology #
Determine whether any social handle (Twitter, Discord) has been associated with a prior rugged or failed project under a different alias.
See the full factor methodology and distribution across all protocols →