A Google employee is said to be connected to several Nintendo leaks that are not safe anywhere

The image does not belong to buddystech.com

June 5, 2024

A bombshell story from 404 Media found a link between several Nintendo hacks and a Google worker. An internal Google database that keeps track of privacy and security problems raised by workers from 2013 to 2018 says that this person watched Nintendo’s private YouTube videos and shared their material online.

The Important Details:

Number One: Google’s Unintentional Role – The leaks cover six years and have an impact on Nintendo statements during that time. The Google worker’s access to private Nintendo movies let them leak sensitive information before it was officially made public.

  1. The investigation and the result – Google did an internal review and found that the leak was “not on purpose.”
  • The exact Nintendo announcements that were changed by these leaks have not been made public.
  1. Other Google Incidents: The same database showed other incidents, such as recording children’s speech by mistake and keeping license plate data from Google Street View cameras. Google also suggested YouTube videos based on what people had watched before they deleted their information.
  2. Verification and Resolution: Google has confirmed what was written in the internal report and made it clear that all problems were “reviewed and resolved at that time.”

Even though the Google worker may not have meant for his actions to affect Nintendo’s shocks, gamers are still interested in which statements were hacked. Even big tech companies can have an unintended effect on the game world. This is a good lesson while we wait for more information.

What do you think about this new idea? Post your answer below! …


*Note that the information given comes from reports and internal systems, and more information may show how bad the leaks really are. * 😮🎟🏍

Learn more

1nintendolife.com

2kotaku.com

3gamespot.com

4msn.com

5eteknix.com

Leave a Comment

Your email address will not be published. Required fields are marked *