DataBreaches.Net

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

[Conti] Ransomware Group In-Depth Analysis

Posted on November 18, 2021 by Dissent

PRODAFT Threat Intelligence (PTI) Team has obtained valuable insights on the inner workings of the Conti ransomware group. The PTI team accessed Conti’s infrastructure and identified the real IP addresses of the servers in question. This report provides unprecedented detail into the way the Conti ransomware gang works, how they select their targets, how many targets they’ve breached, and more.

Their report contains some information that will be a rehash of what has previously been reported by others, but it also discloses some interesting new findings, e.g.:

One of the main objectives of our investigation was revealing the identity of the Conti affiliates, retailers, developers and servers. Our management panel analysis revealed a great deal of information regarding the servers that this group uses. One of the most valuable pieces of threat intelligence we discovered is the the real IP address of Conti’s TOR hidden service and contirecovery.ws, and 217.12.204.135, on Tuesday, 28 September 2021 21:30:03 UTC.

Additionaly, our team was able to identify the operating system details of the server hosting the TOR hidden service for Conti. The host is a Debian server with host name ”dedic-cuprum-617836”. We believe the numeric value at the end of the host name is an invoice number for the server, assigned by the hosting company ITLDC

Analyses provided by Elliptic provided additional in-depth details of payments to Conti wallets:

Of the seven active addresses, four were found to send a percentage of their incoming funds, either directly or indirectly, to the same address cluster (hereafter referred to as “Conti consolidation cluster”). For three of these addresses, almost exactly 22.5% of the original incoming funds were sent to this cluster. As a result, it appears that this consolidation cluster may represent the operator portion of these ransomware payments.

A further 31 incoming flows to this cluster were identified which appear to be ransomware payments. The majority of these send between 22-23% of their incoming funds either directly or indirectly to the Conti consolidation cluster. This common splitting pattern indicates that Conti affiliates may be awarded a percentage of the ransoms they successfully obtain, potentially contradicting CISA’s assessment of Conti operating a wage-based affiliate payment model. Of interest, several further payments were identified in which the incoming funds originate from a split of a previous ransom payment, as demonstrated in the graph below. It is unclear whether this demonstrates an attempt to obfuscate the flow of funds, or a payment to the Conti operator for other services.

Researching the addresses identified by Prodaft and the incoming payments to the consolidation cluster indicates that since July 2021, Conti has received over 500 bitcoin in
ransomware payments, valued at over $25.5 million, of which $6.2 million has been sent to the Conti consolidation cluster.

You can download the full free report here.

 

Related posts:

  • The Myth of Jurisdictional Privacy
  • Threat actors sometimes name the wrong victims — so why are you just repeating their claims?
  • Broward County Public Schools Cyberattack was Ransomware Attack — New Details Emerge
  • “Without Undue Delay,” Part 2
Category: Commentaries and AnalysesMalware

Post navigation

← Tr: MNG Kargo Hacked: User Information Stolen
Brussels health authorities deny data violation on vaccination platform →

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

  • 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
  • Breaches have consequences (sometimes) (1)
  • Kansas City Man Pleads Guilty for Hacking a Non-Profit
  • British national “IntelBroker” charged with causing $25 million in damages; U.S. seeks his extradition from France
  • France issues press statement about arrest of ShinyHunters members
  • Patients Allege Home Delivery Pharmacy Failed to Timely Notify Them of Data Breach
  • Hackers breach Norwegian dam, open valve at full capacity

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

  • Microsoft’s Departing Privacy Chief Calls for Regulator Outreach
  • Nestle USA Settles Suit Over Job-Application Medical Questions
  • NY Attorney General James Affirms Hospitals Must Provide Access to Emergency Abortion Care
  • How Internet of Things devices affect your privacy – even when they’re not yours
  • Sky Views Personal Data as a Potential Weapon in IPTV Piracy War
  • Florida Used a Nationwide Surveillance Camera Network 250 Times To Aid in Immigration Arrests
  • Federal Court Strikes Down HIPAA Reproductive Health Care Privacy Rule

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.