ctipilot.ch

Nintendo employee data stolen from third-party HR-survey SaaS TinyPulse (Shadowbyt3$ extortion)

incident · incident:nintendo-tinypulse-shadowbyt3

Coverage timeline
1
first 2026-06-20 → last 2026-06-20
Briefs
1
1 distinct
Sources cited
2
2 hosts
Sections touched
1
active_threats
Co-occurring entities
0
no co-occurrence

Story timeline

  1. 2026-06-20CTI Daily Brief — 2026-06-20
    active_threatsFirst coverage — third-party HR-SaaS supply-chain data theft; W-9/bank-statement exposure

Where this entity is cited

  • active_threats1

Source distribution

  • bleepingcomputer.com1 (50%)
  • technadu.com1 (50%)

Items in briefs about Nintendo employee data stolen from third-party HR-survey SaaS TinyPulse (Shadowbyt3$ extortion) (1)

Nintendo employee data stolen from third-party HR-survey SaaS (TinyPulse), not Nintendo's own systems

From CTI Daily Brief — 2026-06-20 · published 2026-06-20 · view item permalink →

Nintendo of America confirmed that the extortion group Shadowbyt3$ stole a trove of employee data — not from Nintendo's perimeter, but from TinyPulse, an employee-engagement / pulse-survey SaaS owned by WebMD Health Services (BleepingComputer, 2026-06-18). The exfiltrated dataset (2016–early 2026) reportedly includes employee names, email addresses, W-9 tax forms, bank-statement PDFs and HR analytics (TechNadu, 2026-06-18). The actors demanded USD 2 million from Nintendo on 12 June with a 48-hour deadline; when Nintendo refused, they redirected extortion to TinyPulse directly and began releasing samples. Nintendo characterised the exposure as "internal survey content" for a small subset of employees — narrower than the attacker's claims.

Defender takeaway: HR/engagement SaaS tenants (TinyPulse, Glint, Culture Amp, Leapsome, Qualtrics) routinely store financial-onboarding documents far beyond their nominal survey use-case and are under-weighted in third-party risk reviews. Enforce DLP classification on uploads to these platforms, inventory what data classes each tenant actually retains in its own cloud storage, and treat SSO integrations whose SaaS keeps a separate credential store as a lateral-movement path from one compromised employee credential to the vendor's full dataset.