DataBreaches.Net

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

Maze Team statement ridicules security “experts” and IT administrators who try to cover up breaches

Posted on March 14, 2020 by Dissent

Those who have been watching Maze Team and other ransomware groups are already aware that Maze Team has quietly continued to actively attack entities. Those who do not pay their demands will likely find themselves listed on the threat actors’ website with some of their data publicly dumped for anyone who wants to download it.

Over the past month, the list of victims who have not paid their demands has grown. But if you’re Maze Team, you may not view that list as a growing list of failures on their part, but as a list of successful attacks. However you spin it, we really have no way of knowing how successful their business model actually is. What percent of all their victims are listed on their website? What percent do they need to have pay them to be profitable? If only one victim pays them, but they get millions, isn’t this all still worth their time and effort?

And does listing a victim on the site actually influence victims to pay up?  According to their statement to this site, Stockdale Radiology paid up and that was after they had appeared on the site. But MDLab never paid up, even after the attackers started dumping their data.

Last night, Maze Team issued its own “press release.”  Some of the points they make seem predictable — statements that are actually warnings to current and future victims that if they don’t pay up, Maze Team will basically do whatever the hell it wants with the data and all the blame should fall on the company that failed to prevent the attack and then was careless after they were attacked.

But in this day and age, when most people say that a breach is not a matter of “if” but rather, “when,” will victim blaming carry any weight at all as a pressure technique? Probably not.

After issuing explanations (cautions), Maze Team turned to media coverage of their work (typo’s below are as in the original):

One more word about the Security “Experts” discussing our activity and our team. We are greately disappointed with those so called Professionals who can’t tell the difference between phishing and lateral movement . We don’t need to use phishing attacks and slowly move from one target to another as we have the access to the to the hosting provider . As long as such so called Professional will work in IT and Security we will have a lot of work.

They also had some caustic comments about some of the network administrators they communicated with about their attacks:

Another word for the IT specialist and network administrators who are tring to hide the information of the data leak from the company’s executives. They are making everything just the worst. We were really shoked by the fact that some network administrators were trying to hide the leak by offering us the access to the data of other companys, access to private laptops of the company’s president or even the naked photos of their boss’es secreteary. Funny but it’s true.

We are not interested in accesing accounts or bitcoin wallets of the company’s executives. We are doing what we are doing and no other proposals are accepted.

What great material that could all be for the talk I’ve thought about doing on how NOT to respond to a breach, but sadly, Maze Team declined to tell me more about these responses. Maybe one day they will…..

Category: Commentaries and AnalysesMalware

Post navigation

← Two healthcare-related entities disappeared from Maze Team’s website …. why?
Hungarian Supervisory Authority Issues Guidance on Data Protection and Coronavirus →

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

  • Fresno County fell victim to $1.6M phishing scam in 2020. One suspected has been arrested, another has been indicted.
  • Ransomware Attack on ADP Partner Exposes Broadcom Employee Data
  • Anne Arundel ransomware attack compromised confidential health data, county says
  • Australian national known as “DR32” sentenced in U.S. federal court
  • Alabama Man Sentenced to 14 Months in Connection with Securities and Exchange Commission X Hack that Spiked Bitcoin Prices
  • Japan enacts new Active Cyberdefense Law allowing for offensive cyber operations
  • Breachforums Boss “Pompompurin” to Pay $700k in Healthcare Breach
  • HHS Office for Civil Rights Settles HIPAA Cybersecurity Investigation with Vision Upright MRI
  • Additional 12 Defendants Charged in RICO Conspiracy for over $263 Million Cryptocurrency Thefts, Money Laundering, Home Break-Ins
  • RIBridges firewall worked. But forensic report says hundreds of alarms went unnoticed by Deloitte.

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

  • Massachusetts Senate Committee Approves Robust Comprehensive Privacy Law
  • Montana Becomes First State to Close the Law Enforcement Data Broker Loophole
  • Privacy enforcement under Andrew Ferguson’s FTC
  • “We would be less confidential than Google” – Proton threatens to quit Switzerland over new surveillance law
  • CFPB Quietly Kills Rule to Shield Americans From Data Brokers
  • South Korea fines Temu for data protection violations
  • The BR Privacy & Security Download: May 2025

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.