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.

Endpoint

8/12/2015
09:00 AM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

June Was 'Worst Month Of Malvertising Ever'

Flash zero-days made it easier to deliver ransomware and banking Trojans, and commit click fraud.

June was "the worst month of malvertising basically ever" and Flash zero-day vulnerabilities are partly to blame, says Patrick Belcher, director of security analytics for Invincea. In the first six months of 2015, malvertising was one of the biggest threats to endpoint security, causing an estimated $525 million in damages (related to repair and recovery costs), according to research released today by Invincea.

Invincea says it stopped 2,100 malvertising attacks, all dropping some kind of malware on the endpoint -- mostly ransomware, banking Trojans, or bot code that abuses endpoints for click fraud campaigns. 

The researchers identified a Russian threat actor called "Fessleak," that was particularly prolific, and had carried out more malvertising exploits than anyone else Invincea witnessed this year, using real-time ad platforms to deliver ransomare and the Bedep click fraud bot.

"Fessleak was abusing one company so bad he almost ruined the company," says Belcher. The attacker used the ad platform to deliver the Bedep click fraud bot so often that Blue Coat listed the company as a malicious source. They could have gone out of business, had they not succeeded in ejecting Fessleak, says Belcher.

By the end of the year, Belcher expects that the use of weaponized Microsoft Office documents will overtake malvertising as the leading threat, because the use has recently exploded -- with multiple threat actors using the same Visual Basic scripts, available for free on places like Pastebin, to add malicious payloads to documents. The documents are generally delivered via phishing messages.

These malicious documents were used to deliver Dridex, Zeus, Pony, Zbot, Dyreza payloads. They were also used in "just-in-time" malware attacks, which Invincea called the "dominant trend in malare evolution." In such an attack, the malware is delivered to the endpoint in innocent-looking pieces to avoid detection, then assembled on the endpoint, often using native Windows components as part of the finished product.

The researchers also found that although the threat actors behind the Anthem and White House breaches are very sophisticated, the methods they used to invade the organizations were not particularly complex. In fact -- although they may have used custom malware for part of the attack -- the initial intrusions were both accomplished via spearphishing messages with off-the-shelf Trojans attached. In fact, it was the same basic code, just in different wrapping -- the one in the White House was disguised as a video about an office run by monkeys and at Anthem it appeared as a Citrix software update.

See the full report at http://www.invincea.com/1H-2015-threat-report/.

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Whoopty
50%
50%
Whoopty,
User Rank: Ninja
8/13/2015 | 7:38:20 AM
Best practices
As much as these sorts of threats are worrisome, it's good to know that the best way to combat them is to practice good user security. Not opening documents from unknown sources or if the language in the message feels fishy. Virus checking them before opening anything that seems legitimate isn't a bad plan either. 

At least everyone can do that sortr of thing and there isn't some big, expensive software solution which must be considered. 
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...