MapleStory Universe Security Incident: Timeline and Official Response
The blockchain gaming project MapleStory Universe (MSU) recently disclosed a security incident involving unauthorized access to portions of its off-chain server infrastructure. Upon detection, the team proactively placed all services under maintenance starting at 12:43 PM Beijing Time on November 12, 2026, to mitigate risks and initiate an investigation.
Scope of the Data Exposure
Preliminary findings indicate that the attacker accessed records for a subset of users generated after 07:26 AM on November 5, 2026. The compromised data includes:
- Basic Account Information: Wallet addresses, user nicknames, and profile avatars.
- Activity Logs: Login history, transaction and service activity records, and OpenAPI usage logs.
- Linked Details: Some email addresses and information from connected third-party social media accounts.
Critically, the project has confirmed that the following sensitive information was not exposed: real names, phone numbers, physical addresses, KYC documentation, or payment card information. This suggests that core identity and financial privacy data remains secure.
Asset Security and System Impact
Regarding the paramount concern of user assets, MSU provided clear assurances:
- Blockchain Integrity Uncompromised: All on-chain records and wallet states are intact.
- No Financial Loss: The investigation confirmed no user assets were illicitly transferred or stolen.
- Private Keys Secure: The team reiterated that user wallet private keys are never uploaded to MSU's centralized systems and are solely in users' custody, which is the primary reason assets were unaffected.
The incident also affected MSU's Builder Center. Information for 328 applications registered on the platform was accessed, including some API keys. However, the team emphasized that these exposed keys do not possess permissions to transfer user assets, keeping the risk contained.
Immediate Actions and Next Steps by MSU
Upon identifying the breach, MSU's security team executed several critical countermeasures to contain the incident and fortify systems:
- Immediately severed the attack vector to prevent further unauthorized access.
- Revoked all compromised access credentials and API keys, rendering them inert.
- Replaced all affected servers to eliminate potential backdoors or malware.
The official statement notes that prior to fully restoring services, the team will rotate all operational keys and conduct a thorough security audit of the entire infrastructure. Services remain under maintenance, with a restoration timeline to be announced later.