<\/p>\n
Control of the X account has been regained. Based on the current findings, the compromise was limited to this account. No other accounts or systems were affected.<\/span><\/p>\n The team followed strict security protocols and industry best practices to secure the X account. The exact method of attack remains unknown, but available evidence suggests the team was not at fault.<\/span><\/p>\n The compromise was detected at approximately 15:20 UTC on February 26, 2025. No email notifications were received about changes to email, password, delegation, or two-factor authentication (2FA). The email linked to the X account was secured with Google 2FA, which was not synced to any email addresses. Email logs confirm there was no unauthorized access.<\/span><\/p>\n Source: pump.fun<\/p>\n<\/div>\n No delegations were made by the X account, and it had no connected phone numbers or third-party apps. 2FA was enabled using a physical security key and Google 2FA. The password was regularly updated and stored in a secure password manager. 2FA backups were physically stored in a secure location, and there was no unauthorized access. All passwords were complex, using numbers, letters, and symbols.<\/span><\/p>\n At the time of the compromise, only one person had access, and this individual did not interact with any suspicious links. On-chain evidence from @zachxbt suggests the attacker has been involved in similar incidents, such as Jupiter and WIF. The suspected method involves social engineering employees at X or exploiting internal systems.<\/span><\/p>\n The team continues to analyze the incident and will share updates if new findings emerge. Vigilance remains a priority in monitoring potential security threats.<\/span><\/p>\nIntroducing the Pump.fun Mobile App<\/b><\/h2>\n