DataBreaches.Net

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

Let’s Secure Insurance failed to secure their own data storage. Now they have a breach.

Posted on January 27, 2025January 27, 2025 by Dissent

Kumar Hemant reports:

Let’s Secure Insurance Brokers Pvt Ltd., a prominent Indian insurance brokerage firm, has reportedly fallen victim to ransomware. The perpetrators, identified as the Kill Security (alias KillSec) group, claim to have gained unauthorised access to the company’s data, sparking concerns over potential data breaches.

India has increasingly become a focal point for cyberattacks, with industries ranging from finance to healthcare targeted by sophisticated hacking groups. Let’s Secure Insurance Brokers Pvt Ltd is the latest high-profile name to join the growing list of Indian organisations compromised by ransomware gangs.

Read more at Candid Technology, where the headline is “Indian insurance company Let’s Secure suffers ransomware attack.”

Unlikely to be a Ransomware Attack

It’s a shame that the insurer never read our previous reporting on KillSec. As this site always says, there’s no need to hack when it’s leaking.

KillSec finds exposed databases, downloads data, and then demands payment from the victim to delete the data. If the world thinks that KillSec is accomplished hackers, that’s probably just fine with KillSec, but there’s nothing in these attacks that requires anything other than using a search engine or search service that lists exposed databases.

Nor is there evidence that KillSec is encrypting files of its victims. It’s more of a simple extortion model that capitalizes on databases entities misconfigured.

From Leak to Breach

Like too many others, Let’s Secure Insurance had an unsecured Amazon storage bucket. It was first noted as unsecured on an indexing service on November 22, 2024.  KillSec seems to have noted it, too, and then tried to ransom the data.

The bucket is still unsecured even after KillSec listed them on KillSec’s dark web site yesterday.

Every victim listed on KillSec’s dark website since November had an unsecured cloud storage bucket or blob (usually bucket) that KillSec appears to have found via a service that lists exposed servers.   When examined by the researcher known as JayeLTee and another researcher who wishes to remain anonymous, the data KillSec leaks has been the same data that researchers found in the exposed buckets.

Sadly, most of the victims’ buckets are still unsecured.

If  You Are Contacted by KillSec

  • Check (or have your IT service check) your Amazon AWS s3 buckets to determine which is misconfigured, and lock it down. You’ll likely find it’s an Amazon AWS s3 bucket. Only occasionally have we seen an Azure blob be the source.
  • Be sure to lock the bucket down properly so that even if someone has the file list or file links, they cannot directly connect to the files.
  • Do not pay KillSec. That only encourages more of this type of thing, and besides, if they have your data, how many other unauthorized individuals have your data? Your data are already out there and paying criminals won’t fix that. Hopefully, you have access logs to figure out how many unauthorized IP addresses accessed data back to the time when it was first exposed and you can figure out who needs to be notified.

 

 


Related:

  • PowerSchool commits to strengthened breach measures following engagement with the Privacy Commissioner of Canada
  • Hungarian police arrest suspect in cyberattacks on independent media
  • British institutions to be banned from paying ransoms to Russian hackers
  • Data breach feared after cyberattack on AMEOS hospitals in Germany
  • Inquiry launched after identities of SAS soldiers leaked in fresh data breach
  • Bitcoin holds steady as hackers drain over $40 million from CoinCDX, India's top exchange
Category: Business SectorCommentaries and AnalysesNon-U.S.

Post navigation

← Slovak PM accuses Ukraine — without any evidence — of involvement in alleged “massive cyberattack”
EU sanctions 3 GRU members for cyberattacks against Estonia →

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

  • Scattered Spider Hijacks VMware ESXi to Deploy Ransomware on Critical U.S. Infrastructure
  • Hacker group “Silent Crow” claims responsibility for cyberattack on Russia’s Aeroflot
  • AIIMS ORBO Portal Vulnerability Exposing Sensitive Organ Donor Data Discovered by Researcher
  • Two Data Breaches in Three Years: McKenzie Health
  • Scattered Spider is running a VMware ESXi hacking spree
  • BreachForums — the one that went offline in April — reappears with a new founder/owner
  • Fans React After NASCAR Confirms Ransomware Breach
  • Allianz Life says ‘majority’ of customers’ personal data stolen in cyberattack (1)
  • Infinite Services notifying employees and patients of limited ransomware attack
  • The safe place for women to talk wasn’t so safe: hackers leak 13,000 user photos and IDs from the Tea app

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

  • Congress tries to outlaw AI that jacks up prices based on what it knows about you
  • Microsoft’s controversial Recall feature is now blocked by Brave and AdGuard
  • Trump Administration Issues AI Action Plan and Series of AI Executive Orders
  • Indonesia asked to reassess data privacy terms in new U.S. trade deal
  • Meta Denies Tracking Menstrual Data in Flo Health Privacy Trial
  • Wikipedia seeks to shield contributors from UK law targeting online anonymity
  • British government reportedlu set to back down on secret iCloud backdoor after US pressure

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.