DataBreaches.Net

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

Boomerang continues to demonstrate how NOT to handle a possible breach

Posted on January 23, 2015 by Dissent

On January 13, I wrote:

And for Tuesday’s edition of “How Not to Handle a Reported Breach,” we give you….. (drum roll)…. Boomerang Rentals.

Although Boomerang has continued to investigate claims of a breach resulting in fraudulent charges, and have brought in a third party to assist in their investigation, they still haven’t notified consumers of the situation.

Given that there are reports of fraud, wouldn’t it be prudent of them to notify everyone and say, “Look, we have not found any evidence of any breach of our system, but we’d rather err on the side of caution, so do be careful out there and check your card statements, etc…” ?

But now things have gotten even worse, in my opinion. Seen on Twitter this morning (and sent to me by a reader of this blog):

Wow. @boomeranggames blocked me after I told them about a SQL Injection vulnerability in their site. Really taking security seriously? 🙁

— Danny Tuppeny (@DanTup) January 23, 2015

Yes, Boomerang. Put your head in the sand on Twitter. That’s sure to make things better.

Related posts:

  • UK: Boomerang Rentals customers report fraudulent card charges (Update 2)
  • UK: Warning to SMEs as firm hit by cyber attack fined £60,000
  • A 2020 Data Breach That Continues To Remain An Unsolved Mystery
  • Boomerang still not telling customers whether they’ve confirmed a security breach
Category: Business SectorCommentaries and AnalysesNon-U.S.

Post navigation

← Divorcing parents promise not to write books ‘dealing with’ (moderately famous) autistic son
Payment Processor EgoPay Confirms Hack, Insider Suspected →

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

  • Texas Centers for Infectious Disease Associates Notifies Individuals of Data Breach in 2024
  • Battlefords Union Hospitals notifies patients of employee snooping in their records
  • Alert: Scattered Spider has added North American airline and transportation organizations to their target list
  • Northern Light Health patients affected by security incident at Compumedics; 10 healthcare entities affected
  • Privacy commissioner reviewing reported Ontario Health atHome data breach
  • CMS warns Medicare providers of fraud scheme
  • Ex-student charged with wave of cyber attacks on Sydney uni
  • Detaining Hackers Before the Crime? Tamil Nadu’s Supreme Court Approves Preventive Custody for Cyber Offenders
  • Potential Cyberattack Scrambles Columbia University Computer Systems
  • 222,000 customer records allegedly from Manhattan Parking Group leaked

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

  • Germany Wants Apple, Google to Remove DeepSeek From Their App Stores
  • Supreme Court upholds Texas law requiring age verification on porn sites
  • Justices nix Medicaid ‘right’ to choose doctor, defunding Planned Parenthood in South Carolina
  • European Commission publishes its plan to enable more effective law enforcement access to data
  • Sacred Secrets: The Biblical Case for Privacy and Data Protection
  • Microsoft’s Departing Privacy Chief Calls for Regulator Outreach
  • Nestle USA Settles Suit Over Job-Application Medical Questions

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[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.