mSeven Software is urging current and former mSecure password manager customers to change stored passwords, reset or re-enroll two-factor authentication, and remove existing passkeys after a cyberattack involving the service. The company’s notification, sent to customers on November 3, said it had discovered suspicious activity and launched an investigation with help from external cybersecurity experts.
The notice did not explain which systems were affected, whether customer data had been taken, or how many people might be impacted. It advised customers to take steps to protect confidential information stored in mSecure.
Although mSeven has not publicly detailed the incident, customer support responses shared by users reportedly said a hacker stole an encrypted database from mSecure Cloud. Those responses indicated that it contained information belonging to current and former users who synchronized their password databases through the service. They also said the company had no evidence that the attacker accessed the information inside the database.
mSecure stores passwords, passkeys, financial details and other sensitive information in encrypted vaults that can be synchronized between devices. According to mSeven’s security documentation, data is encrypted locally using AES-256 before being sent to the company’s servers, and the company says it cannot view customers’ decrypted vault contents.
The reported theft has prompted questions from customers about the need to change credentials if the database was encrypted. Stolen vaults can still present a risk if attackers manage to crack weak master passwords using offline methods. Customers have also criticized mSeven for not publicly explaining how the breach occurred or providing more detail about the potential risks.
Support responses reportedly said mSeven had added security measures and had no evidence that the mSecure app was currently unsafe to use. BleepingComputer said it contacted the company with questions about the incident and its impact on customers but had not received a response.
Sources: BleepingComputer.
