Futures
Access hundreds of perpetual contracts
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Futures Kickoff
Get prepared for your futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to experience risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Launchpad
Be early to the next big token project
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
ClawdBot: How did a creator's GitHub account escape hacking?
A concerning incident has just shaken the developer community: Peter Steinberger, founder of ClawdBot, discovered that his GitHub account had been compromised by scammers operating within the crypto ecosystem. This hacking attempt raises critical questions about the security of accounts belonging to public figures in the tech and blockchain sectors.
Discovery of the breach and requests for help
Alerted by suspicious activity, Steinberger immediately reported the incident on platform X, according to reports from PANews. Facing the hacking of his digital identity, the creator of ClawdBot is currently seeking support from the GitHub community to regain access to his account. He clarified several important points: he did not participate in creating suspicious token projects and strongly denied allegations suggesting misuse of his commit history for fraudulent activities.
Origins of the problem: branding and account changes
One reason behind this vulnerability lies in the modifications made to the account. Anthropic, the company associated with the project, demanded a change of account name—a decision that was imposed and not voluntary. At the same time, Steinberger had to adjust the name of ClawdBot for intellectual property and branding reasons. This complex situation resulted in a failure to change the GitHub account name, creating an opening for fraudsters. In response to these complications, vigilant members of the crypto community proactively registered the associated X (formerly Twitter) account name as a protective measure against identity theft.
Lessons for developer security
This incident illustrates how administrative processes and account modifications can create security vulnerabilities. For influential developers and creators of popular projects, vigilance remains essential in the face of identity theft attempts and account hacks orchestrated by malicious actors within the crypto sector.