mSecure breach forces credential reset amid secrecy
mSeven Software warned mSecure customers to reset all stored passwords, 2FA, and passkeys after detecting suspicious activity.

mSeven Software warned mSecure customers on November 3 to change stored passwords, reset two-factor authentication, and delete passkeys. The company confirmed suspicious activity in its password management application but provided no details on systems, timing, or whether vault data was accessed.
mSeven discovered the suspicious activity and launched an investigation with external cybersecurity experts. It did not identify the activity or confirm whether attackers accessed customer vaults. The company did not specify the systems involved, the timing of the activity, whether it has stopped, or how many users were affected. It also did not confirm if vault data or encryption keys were accessed. mSeven faces pressure to publish a timeline and scope statement to rebuild confidence.
Customers face unclear reset requirements
The warning email was sent to current and former customers. It instructed users to reset passwords, 2FA, and delete passkeys but omitted specifics on which data types were affected or how to proceed. mSecure 7 can store passkeys and 2FA codes on its Essentials tier and above, but the email did not clarify which data types required resets.
mSeven did not say whether the reset steps apply to stored items, the account's sign-in, or both. The email did not specify which accounts to prioritize, how to perform the steps, or whether customers should continue using mSecure. The warning applied to all credentials in the vault, not just the master password. Customers with hundreds of stored credentials must perform hours of updates across banking, work, and personal accounts. One customer with over 800 stored passwords questioned if all entries need replacement. Another user with more than 500 credentials questioned if resets apply to each two-factor method and passkey. The notification does not explain whether recommendations are precautionary or based on evidence of credential exposure.
Security and encryption claims remain unchallenged but unverified
mSecure asserts device-level AES-256 encryption and a zero-knowledge architecture. Vault data is encrypted on the customer's device before syncing via mSecure Cloud, Dropbox, iCloud or Wi-Fi, and developers cannot read stored data. A locally generated Account Key, protected by the user’s password, secures the data. mSeven Software said: "We recently learned of suspicious activity linked to the app but do not say what happened or whether anyone's stored data was exposed."
The notification does not confirm whether attackers accessed encrypted vaults, obtained encryption keys, or viewed information in readable form. Customers must assume full exposure and reset credentials without knowing which data was compromised, bearing the operational costs from the vendor's lack of transparency.
External scrutiny highlights potential vulnerabilities
Germany's Federal Office for Information Security (BSI) identified theoretical access risks in an older version of the app. Its study, published in December 2025, found that mSecure 6.1.5 for Android could, in theory, allow access to stored data. The study tested only version 6.1.5 and may not reflect findings on later versions like the newest iPhone version, 7.1.0, released on October 23.
The incident exposes a transparency gap in security communications. Password managers concentrate risk as a single vault may hold hundreds of logins. Security practitioners recommend rotating the most sensitive credentials first, including email, banking and accounts that can reset others. Users on Reddit expressed concern about the need to change hundreds of credentials, uncertainty about the email’s authenticity, and questions about the zero-knowledge security model. Many prioritized changing primary email, financial, and sensitive accounts through official apps or websites.
Regulators in the U.S. and Europe require breach notifications within set windows once personal data exposure is confirmed. The company ended its message with an apology for 'any inconvenience.' mSeven must provide a detailed incident report and timeline to restore user confidence and meet regulatory expectations.





