Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Mobile Security //

Cellular Network

6/29/2018
08:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

'Bad Bots' Invading Cellular Networks

A new research paper from Distil Networks finds that 'bad bots' are roaming cellular networks and are using these gateways as part of numerous attacks.

Distil Networks is a security company that has made bot defense one of its main areas of concern. While the firm seems to be reputable -- StubHub, Lufthansa and Verizon are listed among its clients -- the company's views on bots must be viewed within the context of the business.

However, Distil seems to be onto something.

Its latest threat research report -- "Mobile Bots: The Next Evolution of Bad Bots" -- finds that bot operators are now implementing a new technique, leveraging mobile devices to avoid detection and execute a number of criminal acts.

In the report, researchers examined requests from 100 million mobile devices on its network from six major cellular carriers during a 45-day period.

They found that the most sophisticated "bad bots" have adopted a new morphology.

(Source: Flickr)
(Source: Flickr)

Distil found that the bots were launched from both smart devices and laptops in public places. Not only that -- the new advanced persistent bots (APBs) would use cellular networks to hit their targets.

By connecting through cellular gateways, Distil finds that these mobile bots are hiding in the open and are very unlikely to be picked up by the defensive technique of IP address blocking. The researchers saw that within some cellular networks, a single IP address can cater to more than 4,000 devices per day. This seems to them a perfect place for bad bots to hide.

Distil's research showed that 5.8% of all mobile devices on cellular networks were used in bad bot attacks. They were also responsible for 8% of bad bot traffic. Almost half -- 44% -- of all cellular IP gateways were used in such attacks.

Some of the attacks included web scraping, brute force attacks, competitive data mining, online fraud, account hijacking, data theft, spam and digital ad fraud, according to Distil.

The report also found:

On average, each day there were 15 devices making bad bot requests on every cellular gateway IP address. The maximum number of devices making bad bot requests on one IP during a single day was 862. The average number of bad bot requests per device was 50 per day.

This gives context to how involved this situation can actually be.

To Distil, mitigation includes protecting exposed APIs and mobile apps -- not just the website -- and share blocking information between systems wherever possible. The researchers noted that that protecting your website does little good if backdoor paths remain open.


Boost your understanding of new cybersecurity approaches at Light Reading's Automating Seamless Security event on October 17 in Chicago! Service providers and enterprise receive FREE passes. All others can save 20% off passes using the code LR20 today!

They also recommend blocking certain data centers, including Digital Ocean, OVH SAS, Choopa, LLC, OVH Hosting, GigeNET, and even Amazon, arguing that these are easily accessible hosting and proxy services that could be the kickoff point for a bot maintained by a less sophisticated operator.

"Mobile is the new frontier for bot operators, as they can perform highly advanced attacks while remaining hidden in plain sight," Rami Essaid, chief product and strategy officer at Distil Networks, noted in a statement. "We have seen bot operators develop and enhance their techniques throughout the years, but the threat to mobile devices is real and growing."

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
What the FedEx Logo Taught Me About Cybersecurity
Matt Shea, Head of Federal @ MixMode,  6/4/2021
Edge-DRsplash-10-edge-articles
A View From Inside a Deception
Sara Peters, Senior Editor at Dark Reading,  6/2/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-23394
PUBLISHED: 2021-06-13
The package studio-42/elfinder before 2.1.58 are vulnerable to Remote Code Execution (RCE) via execution of PHP code in a .phar file. NOTE: This only applies if the server parses .phar files as PHP.
CVE-2021-34682
PUBLISHED: 2021-06-12
Receita Federal IRPF 2021 1.7 allows a man-in-the-middle attack against the update feature.
CVE-2021-31811
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an OutOfMemory-Exception while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-31812
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an infinite loop while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-32552
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the openjdk-16 package apport hooks, it could expose private data to other local users.