Skip to content

mSecure Urges Password Resets After Suspicious Activity

mSecure Urges Password Resets After Suspicious Activity

Published November 4, 2026 · Last updated November 4, 2026

Password manager maker mSeven Software has emailed current and former customers about the information stored in mSecure. The company says it detected "suspicious activity" associated with the app. It advises customers to protect their data by changing passwords, resetting two-factor authentication (2FA), and removing passkeys. It has not said what happened, when it happened, or whether any customer data was exposed.

The email is short on detail, so customers are left to judge the risk themselves. Many of them store hundreds of logins in the app.

What the email says

According to the email, mSeven recently learned of suspicious activity connected to the mSecure app. The company says it opened an investigation, took steps to contain the issue, and brought in outside cybersecurity experts [1]. It does not describe the activity, name the affected systems, or say whether the problem is contained.

The advice is conditional. The company says protecting stored information "may include" changing passwords, resetting or re-enrolling 2FA methods, or removing passkeys [1]. That leaves customers to work out which of those steps apply to them.

What the mSeven notice states and what it leaves out The left column lists the items the notice mentions: suspicious activity, and possible password changes, 2FA resets and passkey removal. The right column lists what the notice does not provide: the nature of the activity, when it happened, whether data was exposed, and whether vaults or sign-ins were affected. Stated in the notice • Suspicious activity occurred • Passwords may need changing • 2FA may need resetting • Passkeys may need removing Not stated • What the activity was • When it happened • Whether data was exposed • Vault or sign-in impact Source: mSeven notice as reported by The Register.
The notice mentions several actions but gives no detail about the incident. The dashed box marks what remains unknown.

How customers are reacting

Customers have taken their questions to mSecure's support forum and to Reddit. One user with more than 800 stored passwords asked whether the email meant every one of them had to change. Another, with more than 500, asked whether the 2FA and passkey advice applied to every account or only to the sign-in for mSecure itself [1].

A third customer asked the company to say what remedial action is required and what data was compromised, and called the current wording unacceptable [1]. As of The Register's reporting, mSeven had not responded to its questions.

What the notice leaves unanswered

Several questions matter for deciding what to do next, and the published wording does not settle them.

  • Scope of exposure. The notice does not say whether the activity reached vault contents or the encryption keys that protect them.
  • Which secrets are at risk. The phrase "all confidential information stored" could mean the vault, the mSecure sign-in, or both. Customers have asked exactly this.
  • Sync method. mSecure's support site describes what an account reset does to data in mSecure Cloud, Dropbox, and iCloud [3]. The incident notice does not say whether the risk differs by sync method.
  • Whether to keep using the app. The published wording gives no guidance on this, including whether customers should store newly reset passwords in mSecure.

What the vendor says about how vaults are protected

mSeven's support site says the account password and account key are "only accessible by you." It says they are never stored or shared by mSecure or mSeven. It also says the account password is the only way to decrypt saved data [2].

These are product claims, not findings about this incident. If the design works as described, reading a vault would require both the account password and the account key. That makes it important that the notice does not say whether either was involved.

The same support site says an unauthorized sign-in would mean the attacker had obtained the account email, account password, and encrypted account key [3]. It also says mSecure keeps a copy of your real logins, so changing those passwords at the source makes any stolen copy useless [3].

What to change, and in what order

Not every item on the notice's list means the same thing. The table below separates the common cases.

What is stored What to do Why
Logins for email, banking, work, and cloud accounts Change the password at each official site or app mSecure holds copies of these logins, so changing them at the source makes stolen copies useless [3].
Your mSecure account sign-in Change the account password in the app if you can still unlock it This blocks new access to the vault [3].
2FA codes and passkeys saved in mSecure Re-enroll or remove them as the notice suggests, and check each service's own security settings The notice says this "may" be needed but does not say which items are affected [1].

The vendor's sign-in guidance says to prioritize sensitive accounts, especially financial institutions [3]. Most people will also want to start with email, since a compromised inbox can be used to reset other accounts. That order is general practice, not something the notice or the vendor says.

Watch mSeven's own channels for an actual explanation. Until one appears, the notice is the only official word, and it does not say what happened.

The email ends with "We regret any inconvenience that this may cause." For someone with hundreds of logins, that is a mild phrase for what could mean days of resets. Until mSeven says more, the sensible approach is to treat the warning as serious and work through the most valuable accounts first.

Sources & References

  1. The Register, "Password manager mSecure tells users to change passwords, won't say why," Carly Page, November 3, 2026
  2. mSecure Support, "Account password or forgotten password issues?"
  3. mSecure Support, "Sign-In was not Authorized"
NK

Cybersecurity Researcher & Technical Editor

UnpanicTech publishes independent cybersecurity research and defensive security analysis. Naseem Khan serves as Technical Editor, with a focus on vulnerability analysis, defensive security, incident response, cloud security, and practical security engineering.

Leave a Comment (Authenticated Users)