NINTENDO OF AMERICA INC.
bd_5cb808e15ffa13bf · schema v1 · pii pii-v1
Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Shadowbyt3$ on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
The breach has been confusing some people like they didn't breach nintendo and all that, But are goal wasn't beach nintendo directly but to steal some pii, operational plans, all private chats of employees. This Breach doesn't affect nintendo gaming wise it only affects a small amount of employees that work for nintendo and have used tinypulse. Tinypulse you have till june 16th 2026 to contact us via telegram or email that we have sent you. Nintendo decided to not pay so we are demanding that tinypulse pays or all data will be leaked including private messages on nintendo employees and not all employees are happy we can tell you that. Private messages are about to not become private if tinypulse doesn't reach an agreement with us. This is all we have to say about it no further questions. it's simple if they don't pay there leaked. This is just the file tree of all the data we stole so you can actually see that there are w9 forms with employee id's.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jun 14, 2026
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
shadowbyt3$
According to ransomware.live, ShadowByt3$ is a ransomware-as-a-service group first observed in October 2025, using multi-method extortion and communicating via Telegram and Tox, with a very small confirmed victim list suggesting it remains in early-stage operation.