mSecure: password manager incident, reset 2FA and passkeys
mSeven asks mSecure customers to change passwords, 2FA and passkeys: according to support replies, the encrypted mSecure Cloud database was stolen.

On 3 November 2026 mSeven Software, the US developer of the mSecure password manager, wrote to current and former customers to report “suspicious activity” associated with the application. The news was covered by The Register, heise Security, The Hacker News and BleepingComputer. The company asks users to immediately protect all confidential information stored in mSecure: change passwords, reset or re-enrol two-factor authentication methods and, where needed, remove passkeys.
What the official notice says
In the email, quoted by The Register and BleepingComputer, mSeven says it launched an investigation, took steps to mitigate the issue and engaged external security experts. It does not explain what the suspicious activity was, when it happened, which systems were affected, whether customer data was taken or how many users are involved. Both outlets say they asked the company for clarification and received no reply.
The vagueness of the notice has caused confusion on the support forum and on Reddit: some users, with hundreds of saved credentials (more than 800 in one case), are asking whether they really have to change all of them and whether the advice on 2FA and passkeys covers every account or only access to mSecure itself.
The encrypted mSecure Cloud database
According to BleepingComputer, further detail comes from mSeven support replies that some customers posted on the forum. This is not a public statement by the company, and only one of the four sources reports it:
- an attacker reportedly stole an encrypted database from mSecure Cloud, containing information on current and former users;
- the company reportedly has no evidence that the attacker accessed the confidential content inside the encrypted database;
- the incident reportedly concerns only users who synchronised their data with mSecure Cloud;
- mSeven reportedly added further security measures and has no evidence that the application is unsafe to use today.
Also according to BleepingComputer, mSeven’s documentation describes AES-256 encryption and a zero-knowledge architecture: data is encrypted on the device before being sent to the servers, and the company cannot read the contents of the vaults.
Why a stolen encrypted vault is still a risk
A stolen encrypted vault can be attacked offline, with no limit on attempts and without anyone noticing: its resilience depends on the strength of the master password and on the key derivation function. BleepingComputer recalls the 2022 LastPass case, when backups of encrypted vaults were stolen; researchers later linked the incident to cryptocurrency thefts attributed to the cracking of weak master passwords.
In our reading, this explains why the advice goes beyond passwords: if two-factor authentication seeds (TOTP) or passkeys were stored in the vault, a decrypted vault would expose them together with the passwords. mSeven has not published details on the key derivation it uses or on any unencrypted data in the database.
MITRE ATT&CK techniques relevant to the risk scenario (not observed in the incident, which has not been described):
- T1555.005 – Credentials from Password Stores: Password Managers;
- T1110.002 – Brute Force: Password Cracking, against the stolen copy;
- T1078 – Valid Accounts, if recovered credentials were used.
There are no CVEs and no public indicators of compromise.
Impact for European and Italian organisations
mSecure is mainly a product for individuals and professionals, but employees and consultants often store work credentials in it too: email, VPN, cloud consoles, business applications, API keys. For organisations subject to NIS2, the episode falls under supply chain risk management and credential management; where vaults held access to systems with personal data, it is worth assessing any GDPR implications with the DPO. Healthcare operators should prioritise access to medical records and devices.
What to do now
- Find out who uses mSecure in your organisation and whether they synchronised with mSecure Cloud. Even though support limits the problem to these users, the official notice is addressed to all customers.
- Rotate stored credentials, starting with the most critical: domain and cloud administrators, email, remote access, banking and payments, API keys and application secrets. Changing only the master password does not protect the copy that has already been taken.
- Re-enrol 2FA for accounts whose TOTP seeds were in the vault, and replace passkeys stored in mSecure, revoking the old ones from each service.
- Monitor sign-ins: attempts from unusual countries or networks, newly registered MFA devices, password reset requests, successful logins after a series of failures.
- Watch out for phishing that exploits the incident, with fake mSecure emails or bogus reset notices.
- In the medium term, prefer a business password manager with central administration, and keep phishing-resistant authentication factors for privileged accounts separate from the vault.
How ARXDOME can help
ARX Expose flags company accounts involved in known breaches, which helps decide which credentials to rotate first. ARX Sentry collects events from computers, servers and firewalls and brings them into the SOC pages, where sign-ins to monitored machines can be followed in the weeks that follow.
Last updated:


