Connect with us

Security

Dutch hacker who DDoSed the BBC and Yahoo News gets no jail time

Published

on

Pixelated acronym DDoS made from cubes, mosaic pattern


Timur Arbaev

A Dutch hacker who launched DDoS attacks against high-profile sites like the BBC and Yahoo News, and also attempted to extort many other companies, received no jail time for his actions.

Speaking in a court in the Hague, the Netherlands earlier this month, a 20-year-old man showed remorse in court, admitted to his crimes, which he committed as a minor, and apologized for his actions.

The hacker received 120 hours of community support and 377 days of juvenile detention. He didn’t get any prison time as a part of his sentence was considered time spent and was set free on a 360-day conditional release pursuant he not break any other laws.

S. was a Mirai botnet operator

According to heavily redacted court documents obtained by ZDNet, the hacker managed a DDoS botnet that he built using the Mirai IoT malware. Estimates on the size of the botnets ranged from 2,697 bots (court docs) to 10,000 bots (social media).

Court documents identified the hacker only as S. and did not reveall the names of any of his targets. However, according to a Haagsche Courant journalist present at a February 21 court hearing, some of the websites that suffered from S.’s wrath included the BBC, Yahoo News, e-commerce giant Zalando, and several Bitcoin exchanges and gambling sites.

Authorities say that in some cases, S. also contacted companies asking for Bitcoin ransoms to stop the attacks. One such example is the cryptocurrency exchange Moneypot, which, at the time, published one of S.’s ransom notes.

These attacks happened began around October 2016 and stopped a year later in October 2017, when investigators arrested the suspect.

Evidence from seized equipment included Skype logs detailing conversations with two co-conspirators, one named Chris and another suspect from Croatia.

Conversations included phrases such as “the’re[sic] down and sent email” and “sent this,” with a copy of the email S. had sent.

S. made roughly $150,000

Investigators claim that S. made roughly $150,000 in Bitcoin from his attacks and subsequent ransom demands.

Speaking in court in a February 21 hearing, S. told the judge that he started his DDoS spree because his parents couldn’t give him money due to their financial situation and after learning that the creator of the Mirai IoT malware made $100,000 from a similar scheme. He began using the botnet soon after its source code was released online.

He also said that he first started hacking around 13-14, even before conducting the Mirai-supported DDoS attacks.

Besides confessing and apologizing for his crimes, S. told the judge that he is now involved in cryptocurrency mining and speculation, to which the judge replied that his new occupation is dangerous and that “you will need money again soon.”

The prosecutions asked for a much harsher sentence, with a 24-months prison stay and that S. pay €12,000 ($13,500) in damages to some of the victims.

Multiple industry sources who spoke with ZDNet said that S. is one of the hackers included in a list of top IoT hackers and botnet operators compiled by NewSky Security last year. We have chosen not to include the hacker’s nickname as this was speculation that we could not independently verify.

Related malware and cybercrime coverage:



Source link

Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Security

Phish Fight: Securing Enterprise Communications

Published

on

Yes, much of the world may have moved on from email to social media and culturally dubious TikTok dances, yet traditional electronic mail remains a foundation of business communication. And sadly, it remains a prime vector for malware, data leakage, and phishing attacks that can undermine enterprise protections. It doesn’t have to be that way.

In a just released report titled “GigaOm Radar for Phishing Prevention and Detection,” GigaOm Analyst Simon Gibson surveyed more than a dozen enterprise-focused email security solutions. He found a range of approaches to securing communications that often can be fitted together to provide critical, defense-in-depth protection against even determined attackers.

Figure 1. GigaOm Radar for Email Phishing Prevention and Detection

“When evaluating these vendors and their solutions, it is important to consider your own business and workflow,” Gibson writes in the report, stressing the need to deploy solutions that best address your organization’s business workflow and email traffic. “For some it may be preferable to settle on one comprehensive solution, while for others building a best-of-breed architecture from multiple vendors may be preferable.”

In a field of competent solutions, Gibson found that Forcepoint, purchased recently by Raytheon, stood apart thanks to the layered protections provided by its Advanced Classification Engine. Area 1 and Zimperium, meanwhile, are both leaders that exhibit significant momentum, with Area 1 boosted by its recent solution partnership with Virtru, and Zimperium excelling in its deep commitment to mobile message security.

A mobile focus is timely, Gibson says in a video interview for GigaOm. He says companies are “tuning the spigot on” and enabling unprecedented access and reliance on mobile devices, which is creating an urgent need to get ahead of threats.

Gibson’s conclusion in the report? He singles out three things: Defense in depth, awareness of existing patterns and infrastructure, and a healthy respect for the “human factor” that can make security so hard to lock down.

Continue Reading

Security

When Is a DevSecOps Vendor Not a DevSecOps Vendor?

Published

on

DevOps’ general aim is to enable a more efficient process for producing software and technology solutions and bringing stakeholders together to speed up delivery. But we know from experience that this inherently creative, outcome-driven approach often forgets about one thing until too late in the process—security. Too often, security is brought into the timeline just before deployment, risking last minute headaches and major delays. The security team is pushed into being the Greek chorus of the process, “ruining everyone’s fun” by demanding changes and slowing things down.

But as we know, in the complex, multi-cloud and containerized environment we find ourselves in, security is becoming more important and challenging than ever. And the costs of security failure are not only measured in slower deployment, but in compliance breaches and reputational damage.

The term “DevSecOps” has been coined to characterize how security needs to be at the heart of the DevOps process. This is in part principle and part tools. As a principle, DevSecOps fits with the concept of “shifting left,” that is, ensuring that security is treated as early as possible in the development process. So far, so simple.

From a tooling perspective, however, things get more complicated, not least because the market has seen a number of platforms marketing themselves as DevSecOps. As we have been writing our Key Criteria report on the subject, we have learned that not all DevSecOps vendors are necessarily DevSecOps vendors. Specifically, we have learned to distinguish capabilities that directly enable the goals of DevSecOps from a process perspective, from those designed to support DevSecOps practices. We could define them as: “Those that do, and those that help.”

This is how to tell the two types of vendor apart and how to use them.

Vendors Enabling DevSecOps: “Tools That Do”

A number of tools work to facilitate the DevSecOps process -– let’s bite the bullet and call them DevSecOps tools. They help teams set out each stage of software development, bringing siloed teams together behind a unified vision that allows fast, high-quality development, with security considerations at its core. DevSecOps tools work across the development process, for example:

  • Create: Help to set and implement policy
  • Develop: Apply guidance to the process and aid its implementation
  • Test: Facilitate and guide security testing procedures
  • Deploy: Provide reports to assure confidence to deploy the application

The key element that sets these tool sets apart is the ability to automate and reduce friction within the development process. They will prompt action, stop a team from moving from one stage to another if the process has not adequately addressed security concerns, and guide the roadmap for the development from start to finish.

Supporting DevSecOps: “Tools That Help”

In this category we place those tools which aid the execution, and monitoring, of good DevSecOps principles. Security scanning and application/infrastructure hardening tools are a key element of these processes: Software composition analysis (SCA) forms a part of the development stage, static/dynamic application security testing (SAST/DAST) is integral to the test stage and runtime app protection (RASP) is a key to the Deploy stage.

Tools like this are a vital part of the security layer of security tooling, especially just before deployment – and they often come with APIs so they can be plugged into the CI/CD process. However, while these capabilities are very important to DevSecOps, they can be seen in more of a supporting role, rather than being DevSecOps tools per se.

DevSecOps-washing is not a good idea for the enterprise

While one might argue that security should never have been shifted right, DevSecOps exists to ensure that security best practices take place across the development lifecycle. A corollary exists to the idea of “tools that help,” namely that organizations implementing these tools are not “doing DevSecOps,” any more than vendors providing these tools are DevSecOps vendors.

The only way to “do” DevSecOps is to fully embrace security at a process management and governance level: This means assessing risk, defining policy, setting review gates, and disallowing progress for insecure deliverables. Organizations that embrace DevSecOps can get help from what we are calling DevSecOps tools, as well as from scanning and hardening tools that help support its goals.

At the end of the day, all security and governance boils down to risk: If you buy a scanning tool so you can check a box that says “DevSecOps,” you are potentially adding to your risk posture, rather than mitigating it. So, get your DevSecOps strategy fixed first, then consider how you can add automation, visibility, and control using “tools that do,” as well as benefit from “tools that help.”

Continue Reading

Security

High Performance Application Security Testing

Published

on

This free 1-hour webinar from GigaOm Research. It is hosted by an expert in Application and API testing, and GigaOm analyst, Jake Dolezal. His presentation will focus on the results of high performance testing we completed against two security mechanisms: ModSecurity on NGINX and NGINX App Protect. Additionally, we tested the AWS Web Application Firewall (WAF) as a fully managed security offering.

While performance is important, it is only one criterion for a Web Application Firewall selection. The results of the report are revealing about these platforms. The methodology will be shown with clarity and transparency on how you might replicate these tests to mimic your own workloads and requirements.

Register now to join GigaOm and sponsor NGINX for this free expert webinar.

Continue Reading

Trending