www.twingate.com
Open in
urlscan Pro
2600:1901:0:1d27::
Public Scan
URL:
https://www.twingate.com/blog/tips/ubisoft-data-breach
Submission: On September 14 via api from US — Scanned from DE
Submission: On September 14 via api from US — Scanned from DE
Form analysis
0 forms found in the DOMText Content
We use cookies to provide a better experience, tailor and measure ads, analyze traffic, and personalize content. Click Accept All to consent to use of all cookies. Learn more Customize Reject All Accept All Customize Consent Preferences We use first-party and third-party cookies to provide a better experience, tailor and measure ads, analyze traffic, and personalize content. See Section 4 of our Privacy Policy to learn more. We have categorized the cookies we use and provided detailed information about them below.... Show more NecessaryAlways Active Necessary cookies are required for this website to function and cannot be disabled. They are usually only set in response to actions made by you which amount to a request for services, such as saving your consent preferences or providing secure sign in. You can set your browser to block or alert you about these cookies, but some parts of the site will not work correctly without them. * Cookie li_gc * Duration 6 months * Description Used by LinkedIn to store consent of guests regarding the use of cookies for non-essential purposes. * Cookie device_id * Duration 1 year * Description Cookie used to maintain a local copy of the user's unique identifier. * Cookie _GRECAPTCHA * Duration 6 months * Description This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. * Cookie __cfruid * Duration session * Description Cloudflare sets this cookie to identify trusted web traffic. * Cookie _zendesk_shared_session * Duration session * Description See https://support.zendesk.com/hc/en-us/articles/4408824378650-Zendesk-In-Product-Cookie-Policy * Cookie _zendesk_session * Duration session * Description See https://support.zendesk.com/hc/en-us/articles/4408824378650-Zendesk-In-Product-Cookie-Policy * Cookie _zendesk_authenticated * Duration past * Description See https://support.zendesk.com/hc/en-us/articles/4408824378650-Zendesk-In-Product-Cookie-Policy * Cookie _help_center_session * Duration session * Description See https://support.zendesk.com/hc/en-us/articles/4408824378650-Zendesk-In-Product-Cookie-Policy * Cookie cookieyes-consent * Duration 1 year * Description CookieYes sets this cookie to remember users' consent preferences so that their preferences are respected on their subsequent visits to this site. It does not collect or store any personal information of the site visitors. * Cookie destination_url * Duration session * Description Used during login to redirect to the requested page * Cookie intercom-id-* * Duration 8 months 26 days 1 hour * Description Intercom sets this cookie that allows visitors to see any conversations they've had on Intercom websites. * Cookie intercom-session-* * Duration 7 days * Description Intercom sets this cookie that allows visitors to see any conversations they've had on Intercom websites. * Cookie intercom-device-id-* * Duration 8 months 26 days 1 hour * Description Intercom sets this cookie that allows visitors to see any conversations they've had on Intercom websites. * Cookie cf_clearance * Duration 1 year * Description This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. * Cookie _cfuvid * Duration session * Description This cookie is a part of the services provided by Cloudflare - Including load-balancing, deliverance of website content and serving DNS connection for website operators. * Cookie rc::a * Duration Never Expires * Description This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. * Cookie rc::f * Duration Never Expires * Description This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. * Cookie rc::c * Duration session * Description This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. * Cookie rc::b * Duration session * Description This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. Functional Functional cookies enable this website to provide enhanced functionality and personalization, such as in connection with sharing the content of the website on social media platforms, collecting feedback, and other third-party features. These cookies may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly. * Cookie __cf_bm * Duration 1 hour * Description This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. * Cookie VISITOR_INFO1_LIVE * Duration 6 months * Description A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. * Cookie __hssc * Duration 1 hour * Description HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. * Cookie ytidb::LAST_RESULT_ENTRY_KEY * Duration Never Expires * Description The cookie ytidb::LAST_RESULT_ENTRY_KEY is used by YouTube to store the last search result entry that was clicked by the user. This information is used to improve the user experience by providing more relevant search results in the future. Analytics Analytics cookies are used to understand how visitors interact with our website, such as by counting visits to pages and identifying sources of traffic. This allows us to measure and improve the performance of our website, and identify potential technical issues. If you do not allow these cookies, we will not be able be able to track your visits to our website for the purpose of monitoring its performance. * Cookie _clck * Duration 1 year * Description Used by Microsoft Clarity. The cookie is set by embedded Microsoft Clarity scripts. The purpose of this cookie is for heatmap and session recording. * Cookie _clsk * Duration 1 day * Description Used by Microsoft Clarity. The cookie is set by embedded Microsoft Clarity scripts. Connects multiple page views by a user into a single Clarity session recording. * Cookie _gid * Duration 1 day * Description Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. * Cookie _ga * Duration 1 year 1 month 4 days * Description The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. * Cookie __hssrc * Duration session * Description This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. * Cookie YSC * Duration session * Description YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. * Cookie __hstc * Duration 6 months * Description This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). * Cookie hubspotutk * Duration 6 months * Description HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. * Cookie _gat * Duration 1 minute * Description This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites. * Cookie cb_user_id * Duration 1 year * Description Clearbit cookie for tracking user identity, * Cookie cb_group_id * Duration 1 year * Description Clearbit cookie for tracking accesses from companies. * Cookie cb_anonymous_id * Duration 1 year * Description Clearbit cookie for attributing page views back to an anonyous site visitor. * Cookie pfjs%3Acookies * Duration 1 year * Description Used to check if the user's browser supports cookies. * Cookie _ga_* * Duration 1 year 1 month 4 days * Description Google Analytics sets this cookie to store and count page views. * Cookie FPLC * Duration 20 hours * Description Google Tag Manager sets this cookie for tracking between domains. * Cookie FPID * Duration 1 year 1 month 4 days * Description Google Tag Manager sets this cookie for server-side tagging. Marketing & Advertising Marketing cookies help to deliver advertising that's more relevant to you. They may also be used to limit the number of times you see an advertisement and measure the effectiveness of advertising campaigns. These are third party cookies provided by our advertising partners. If you disable these cookies, you may still receive advertisements, but they will not be personalized based on your activity on this website. * Cookie _rdt_uuid * Duration 3 months * Description This cookie is set by Reddit to help build a profile of your interests and show you relevant ads. * Cookie muc_ads * Duration 1 year 1 month 4 days * Description Set by Twitter to collect data on user behavior and interactions in order to optimize and make advertisements more relevant. * Cookie MUID * Duration 1 year 24 days 1 minute * Description Bing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations. * Cookie personalization_id * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to integrate and share features for social media and also store information about how the user uses the website, for tracking and targeting. * Cookie _fbp * Duration 3 months * Description This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. * Cookie _gcl_au * Duration 3 months * Description Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. * Cookie bcookie * Duration 1 year * Description LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. * Cookie lidc * Duration 1 day * Description LinkedIn sets the lidc cookie to facilitate data center selection. * Cookie _uetsid * Duration 1 day 1 minute * Description Bing Ads sets this cookie to engage with a user that has previously visited the website. * Cookie _uetvid * Duration 1 year 24 days 1 minute * Description Bing Ads sets this cookie to engage with a user that has previously visited the website. * Cookie __gtm_campaign_url * Duration session * Description This cookie is used to collect campaign information from the referring URL and is used to improve advertising campaign relevance. * Cookie test_cookie * Duration 16 minutes * Description The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. * Cookie IDE * Duration 1 year 24 days 1 minute * Description Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. * Cookie __tld__ * Duration session * Description Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences. * Cookie __gtm_referrer * Duration session * Description Used to track the performance of our advertising campaigns. * Cookie cb%3Atest * Duration 1 year * Description Tracks page views and traits for Clearbit. * Cookie VISITOR_PRIVACY_METADATA * Duration 6 months * Description YouTube sets this cookie to store the user's cookie consent state for the current domain. Reject All Save My Preferences Accept All Secure CI/CD Pipelines with ZTNA Workshop Sept 17 Register today Try Twingate Request a Demo Product Docs Resources Partners Customers Pricing Product Docs Partners Resources Customers Pricing Sign in Request Demo Try for Free Blog / What happened in the UbiSoft data breach? Latest News Insights Tips Tutorials Comparisons Glossary Other WHAT HAPPENED IN THE UBISOFT DATA BREACH? Twingate Team • May 23, 2024 In July 2013, Ubisoft, a prominent video game publisher, experienced a data breach involving unauthorized access to user information. The company did not disclose the specific number of users affected or the exact method of the breach. HOW MANY ACCOUNTS WERE COMPROMISED? The breach impacted data related to approximately 58 million users. WHAT DATA WAS LEAKED? The data exposed in the breach included user names, email addresses, encrypted passwords, and potentially other personal details such as SSNs, geographic locations, and phone numbers. HOW WAS UBISOFT HACKED? Hackers allegedly gained access to Ubisoft systems and accounts for approximately 48 hours before the company revoked their access. During this time, the attackers audited users' access rights and thoroughly reviewed Microsoft Teams, Confluence, and SharePoint. The exact vulnerabilities exploited by the hackers were not disclosed. UBISOFT'S SOLUTION In response to the hack, Ubisoft took action by initiating a company-wide password reset as a precautionary measure. They also worked with leading external experts to investigate the issue. While there is no explicit mention of enhanced security protocols or notifying affected customers, Ubisoft confirmed that there was no evidence of any player personal information being accessed or exposed as a by-product of the incident. HOW DO I KNOW IF I WAS AFFECTED? Ubisoft did not explicitly mention reaching out to affected users in their response to the breach. If you believe you may have been affected, you can visit Have I Been Pwned to check your credentials for any potential exposure in this or other data breaches. WHAT SHOULD AFFECTED USERS DO? In general, affected users should: 1. Change Your Password: Immediately update your password for the affected platform. Make sure the new password is strong and unique, not previously used on any other platform. 2. Reset Passwords for Other Accounts: If you've used the same or similar passwords for other online accounts, reset those as well. This is crucial as attackers often try using stolen passwords on multiple sites. 3. Enable Two-Factor Authentication (2FA): Activate 2FA on the affected account. Consider enabling this additional security feature on all other important online accounts to significantly reduce the risk of unauthorized access. For more specific help and instructions related to Ubisoft's data breach, please contact Ubisoft Support directly. WHERE CAN I GO TO LEARN MORE? If you want to find more information on the Ubisoft data breach, check out the following news articles: * Ubisoft Cyber Security Incident Update * Game studio Ubisoft examines claims of data security incident Rapidly implement a modern Zero Trust network that is more secure and maintainable than VPNs. Try Twingate for Free Request Demo Solutions Zero Trust Access Documentation Quick Start Use Cases Architecture API Twingate Labs Resources Blog Customers Whitepaper Changelog Company About Careers Pricing Partners Terms Privacy Your Privacy Choices Support Contact Sales Get Help FAQ Try for Free Request Demo Download Copyright © 2024 Twingate. All Systems Operational↗ macOS Windows Linux Chrome iOS Android