Vulnerabilities / Threats

4/30/2018
08:15 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Old Worm, New Tricks: FacexWorm Targets Crypto Platforms

Malicious Chrome extension FacexWorm has reappeared with new capabilities, targeting cryptocurrency platforms and lifting user data.

FacexWorm, a malicious Chrome extension, has been rediscovered targeting cryptocurrency trading platforms and spreading via Facebook Messenger. The Cyber Safety Solutions team at Trend Micro reports it's packing a few new capabilities, including the ability to steal user data.

The extension was first detected in August 2017 and returned the following April amid reports of increased appearances in Germany, Tunisia, Japan, Taiwan, South Korea, and Spain. Like the original, it sends socially-engineered links to friends of affected Facebook account holders.

Unlike the original, it steals accounts and credentials related to FacexWorm's targeted sites. The attack takes potential victims to websites where it injects malicious cryptomining code and redirects to the attacker's referral link for crypto-related referral programs. It hijacks transactions in trading platforms by replacing the recipient address with the attacker's.

The attacker gets a referral incentive every time a victim registers an account, researchers report. Targeted websites include Binance, DigitalOcean, FreeBitco.in, FreeDoge.co.in, and HashFlare.

FacexWorm arrives on victims' machines via socially-engineered Facebook links. Those who click are redirected to a fake YouTube page where they are prompted to install a codec extension (FacexWorm) to play a video. The extension requests privilege to access and edit data on the site.

If permission is granted, FacexWorm downloads malicious codes from its command-and-control server, opens Facebook's website, and checks to see if the propagation function is turned on. If it is, the extension requests an OAuth token from Facebook and begins obtaining the target account's friend list. Contacts who are online or idle are sent fake YouTube links.

"FacexWorm is a clone of a normal Chrome extension but injected with short code containing its main routine," explains Trend Micro fraud researcher Joseph Chen in a blog post on the finding. The threat downloads more code from the C&C server when the browser is opened.

"Every time a victim opens a new webpage, FacexWorm will query its C&C server to find and retrieve another JavaScript code (hosted on a Github repository) and execute its behaviors on that webpage." This JavaScript code, or miner, is an obfuscated Coinhive script connected to a Coinhive pool, configured to use 20% of the target system's CPU power for each threat.

FacexWorm exhibits other malicious behaviors like stealing account credentials for Google, MyMonero, and Coinhive. This threat targets a total of 52 cryptocurrency platforms. When it detects anyone accessing any of them or using keywords like "blockchain" or "ethereum" in the URL, it redirects the user to a fraudulent webpage.

This threat only works in Chrome. If the malicious link is accessed through any browser other than the Chrome desktop version, it redirects to a random advertisement. Trend Micro has only spotted one Bitcoin transaction compromised by FacexWorm based on monitoring the attacker's wallet. Researchers haven't determined how much money the threat has generated.

Related Content:

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
4/30/2018 | 11:09:11 PM
Performance Impact
I would be surpirsed if this gained legs. If a user takes a 20% cpu hit they are most likely going to report a performance impact.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
4/30/2018 | 11:07:03 PM
Facebook
Talk about kicking facebook while their down. Using Facebook messenger as the medium seems apropos. 
6 Ways Greed Has a Negative Effect on Cybersecurity
Joshua Goldfarb, Co-founder & Chief Product Officer, IDRRA ,  6/11/2018
Weaponizing IPv6 to Bypass IPv4 Security
John Anderson, Principal Security Consultant, Trustwave Spiderlabs,  6/12/2018
'Shift Left' & the Connected Car
Rohit Sethi, COO of Security Compass,  6/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-12026
PUBLISHED: 2018-06-17
During the spawning of a malicious Passenger-managed application, SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows such applications to replace key files or directories in the spawning communication directory with symlinks. This then could result in arbitrary reads and writes, which in tur...
CVE-2018-12027
PUBLISHED: 2018-06-17
An Insecure Permissions vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 causes information disclosure in the following situation: given a Passenger-spawned application process that reports that it listens on a certain Unix domain socket, if any of the parent directories of said ...
CVE-2018-12028
PUBLISHED: 2018-06-17
An Incorrect Access Control vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows a Passenger-managed malicious application, upon spawning a child process, to report an arbitrary different PID back to Passenger's process manager. If the malicious application then generates an e...
CVE-2018-12029
PUBLISHED: 2018-06-17
A race condition in the nginx module in Phusion Passenger 3.x through 5.x before 5.3.2 allows local escalation of privileges when a non-standard passenger_instance_registry_dir with insufficiently strict permissions is configured. Replacing a file with a symlink after the file was created, but befor...
CVE-2018-12071
PUBLISHED: 2018-06-17
A Session Fixation issue exists in CodeIgniter before 3.1.9 because session.use_strict_mode in the Session Library was mishandled.