mSpy data leak: “parental control” spyware repurposed

← All articles
Data protection · EN

mSpy data leak: “parental control” spyware repurposed

Investigations in Germany by netzpolitik.org together with SWR reveal a trove of 3.6 million customer‑support tickets (2014–2024) from the spyware vendor mSpy. The correspondence shows widespread use of the tool to secretly monitor adult partners, not just children.

Secret surveillance of adults via stalkerware can trigger multiple offences in Germany, including § 202a StGB (data espionage), § 202b StGB (interception of data), § 202c StGB (preparation of such acts), and § 238 StGB (stalking), with § 238 now expressly recognising the use of software whose purpose is to digitally spy on others as a particularly serious case.

Within the EU/DE, covert hardware (i.e., disguised microphones/cameras or certain trackers) is banned from the market and even possession can be illegal. Yet general‑purpose “parental control” software remains available and is frequently misused as stalkerware.

The reporting points to shell‑company structures and cross‑border setups make civil enforcement (e.g., GDPR claims) and criminal prosecution against the supplier difficult, even where end‑user conduct is plainly unlawful. Civil‑society groups such as GFF (SpywareShield initiative) are therefore pushing for tighter EU‑wide restrictions on commercial spyware.

There is plenty you can do:

1) Zero‑tolerance policy for stalkerware on corporate or BYOD assets: Clearly prohibit the installation of covert monitoring tools on any device that can access corporate data. Enforce via MDM/MAM and mobile EDR with indicators of stalkerware/Trojan behaviour.
2) Hardened mobile baseline: Require current OS versions, secure boot, and locked‑down sideloading; restrict administrative privileges and mandate store‑only app installs.
3) User awareness as safeguarding: Train staff to recognise digital abuse patterns (unexpected battery drain, unknown device admin apps, suspicious “parental control” prompts) and provide a confidential reporting channel.
4) Incident response for suspected stalkerware: Treat detections as people‑risk as well as data‑risk: preserve evidence safely, avoid tipping off the suspected abuser, and coordinate with HR/legal.
5) Third‑party risk management: If you must use monitoring tooling (e.g., corporate MDM), conduct due diligence on vendor ownership, support practices, data handling, and prior breaches; the mSpy history shows why.

Bottom line: mSpy is a textbook example of dual‑use tech drifting into digital partner violence. Criminal law already covers the use against adults; now regulators and platforms must address supply‑side accountability.

This post has an image on LinkedIn. View on LinkedIn →

Discuss on LinkedIn