Skip to content
NewA calmer, faster ZeroHour
StoryData breachmedium

mSecure Password Manager Warns Users After Suspicious Activity

6 sources · 6 articlesFirst reported Updated ()
What's new

November 4: Malwarebytes Labs reports no details on incident trigger or scope of exposure and advises not to assume data was stolen.

Merged summary · x-ai/grok-4.7 · rewritten as coverage arrivesSummaries by Vani AI

mSeven Software urges mSecure users to change passwords, reset 2FA and remove passkeys after detecting suspicious activity, with reports of possible encrypted database theft from cloud service.

mSeven Software detected suspicious activity in the mSecure password manager and emailed current and former customers on November 3 urging them to change stored passwords, reset or re-enroll two-factor methods, and remove passkeys. The company started an investigation, reduced risk, and hired outside experts but has not disclosed what occurred, when it happened, or whether customer data was accessed. BleepingComputer reports an encrypted database containing customer vaults was stolen from the mSecure Cloud service, though the company states it cannot access decrypted contents and has no evidence the attacker accessed them. Only users who synced via mSecure Cloud are affected.

Key facts
  • Email sent November 3 to customers and former users urging password changes, 2FA resets, and passkey removal
  • Investigation launched with external experts; no details on timeline or number of affected customers
  • Encrypted database stolen from mSecure Cloud per BleepingComputer; company cannot access decrypted contents
  • AES-256 zero-knowledge encryption design
  • Sync options include mSecure Cloud, Dropbox, iCloud, and Wi-Fi
  • Separate December 2025 BSI review not linked to incident
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

Timeline

dated events in the reporting · oldest first
  1. Nov 3, 2026mSeven emails customers about suspicious activity · The Register
  2. Nov 3, 2026mSeven starts investigation and reduces risk · Cyber Security News
  3. Nov 4, 2026BleepingComputer reports encrypted database stolen from cloud · BleepingComputer
  4. Nov 4, 2026Malwarebytes Labs publishes notice of vague incident details · Malwarebytes Labs

What each outlet adds

beyond the shared facts
  • BleepingComputerreports encrypted database stolen from mSecure Cloud and only Cloud users affected
  • Malwarebytes Labsno details on incident trigger or scope and advises not to assume theft
  • The Registercompany did not answer questions about exposed data or timeline
  • Cyber Security Newsseparate BSI review not linked to incident
  • GBHackersblanket password changes suggest potential vault exposure and notes fake hack emails

Coverage

oldest first · one row per article · UTC
  1. · 6d ago The Register · SecurityFirst report

    mSecure tells users to reset passwords and will not say why

    A November 3 customer email recommends password, 2FA, and passkey changes but names no exposed data.

  2. · 6d ago Cyber Security News

    mSecure urges password and passkey resets after suspicious activity

    mSeven has not said whether vaults were accessed, how many customers are affected, or what occurred.

  3. · 5d ago The Hacker News

    mSecure warns customers about suspicious activity

    mSeven Software urges mSecure users to change passwords, reset 2FA and remove passkeys after suspicious activity on November 3, 2026.

  4. · 5d ago GBHackers

    mSecure Password Manager Reports Suspicious Activity Urging Password Changes

    Company advises users to change all stored passwords after detecting suspicious activity.

  5. · 5d ago BleepingComputer

    mSecure password manager encrypted database stolen

    mSeven Software warns customers who synced with mSecure Cloud to change passwords and remove passkeys after an encrypted database was stolen.

  6. · 4d ago Malwarebytes Labs

    mSecure warns users of suspicious activity

    mSeven Software detected suspicious activity in mSecure but did not disclose details, scope or affected users.