DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Trillian Blog and Forums Security Incident

Posted on July 6, 2016 by Dissent

Thanks to the reader who sent in a link to this announcement from Cerulean. Without comment (I think readers can guess what it would be)

What happened?

On July 4th, 2016, a security breach and data disclosure related to a single server that powered the now-retired blog and forums occurred. We became aware of the breach the next day, July 5th, 2016, and immediately shut down the machine and retired it permanently for further forensic analysis. The vulnerability was specific to our deployment of vBulletin, and the intruders used this vulnerability to also extract information from our WordPress blog. Information taken was limited to the user databases, including salted MD5 hashed passwords, for both our WordPress blog and vBulletin forums. Because both of these services had already been deprecated and were only kept online for archival purposes, most of the data was anywhere from 3 to 14 years old. The resulting likelihood of the data being useful to an attacker is therefore much lower unless you’ve used the same password for many years across multiple sites.

If your information for either our blog or forums was taken, you should have received, or will receive, an email from us notifying you of the incident and pointing you to this FAQ.

Am I affected?

Only those customers who had specifically registered to post comments on our blog or participate on our forums were impacted.  No actual Trillian intrusion took place in terms of Trillian passwords, Trillian account data, Trillian messaging data (including cloud history), or Trillian billing information. Because the blog and forums were running third-party code in the form of WordPress and vBulletin, we carefully isolated them from the rest of our network many years ago.

What do I need to do?

If you used the same password on our forums or blog as you do Trillian itself, we urge you to change your Trillian password ASAP. Instructions for changing your Trillian password can be found here. In addition, if you used the same password on our forums or on our blog as you do anywhere else on the internet, we also urge you to also change that password ASAP. While the stolen passwords were hashed, modern computational power makes targetting a specific password well within the realm of possibility. Practice password safety by always using a different password for each site and taking advantage of a password manager to make doing so bearable.

Next steps?

Because the impacted machine has been taken offline completely and will stay offline, the major ongoing concern for customers is if your blog or forum password was shared with another service, including Trillian itself.  Please feel free to contact us directly with any additional questions or concerns, and please accept our sincere apologies. We’re working internally to address the incident and making every effort to ensure nothing like it happens again.


Related:

  • US company with access to biggest telecom firms uncovers breach by nation-state hackers
  • UK: FCA fines former employee of Virgin Media O2 for data protection breach
  • The 4TB time bomb: when EY's cloud went public (and what it taught us)
  • Toys “R” Us Canada customers notified of breach of personal information
  • Gatineau gymnastics centre warns members of possible data breach
  • Hotel and Casino near Las Vegas Strip suffers data breach, documents say
Category: Business Sector

Post navigation

← Chicago man pleads guilty in celebrity iCloud data breach
UK ‘Serious Incident’: East Riding patients medical records lost by company paid to keep them safe →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Threat actors have reportedly launched yet another campaign involving an application connected to Salesforce
  • Russian hackers target IVF clinics across UK used by thousands of couples
  • US, allies sanction Russian bulletproof hosting services for ransomware support
  • Researchers claim ‘largest leak ever’ after uncovering WhatsApp enumeration flaw
  • Large medical lab in South Africa suffers multiple data breaches
  • Report released on PowerSchool cyber attack
  • Sue The Hackers – Google Sues Over Phishing as a Service
  • Princeton University Data Breach Impacts Alumni, Students, Employees
  • Eurofiber admits crooks swiped data from French unit after cyberattack
  • Five major changes to the regulation of cybersecurity in the UK under the Cyber Security and Resilience Bill

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Closing the Privacy Gap: HIPRA Targets Health Apps and Wearables
  • Researchers claim ‘largest leak ever’ after uncovering WhatsApp enumeration flaw
  • CIPL Publishes Discussion Paper Comparing U.S. State Privacy Law Definitions of Personal Data and Sensitive Data
  • India’s Digital Personal Data Protection Act 2023 brought into force
  • Five major changes to the regulation of cybersecurity in the UK under the Cyber Security and Resilience Bill

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.