MVISION Insights: DVR Device Vulnerabilities Targeted by FreakOut Botnet
Technical Articles ID:
KB95157
Last Modified: 1/13/2022
Environment
IMPORTANT: This Knowledge Base article discusses a specific threat that is being automatically tracked by MVISION Insights technology. The content is intended for use by MVISION Insights users, but is provided for general knowledge to all McAfee Enterprise customers. Contact McAfee Enterprise for more information about MVISION Insights.
Summary
Description of Campaign
The FreakOut (aka Necro, Necro Python, Necromorph and N3Cr0m0rPh) Botnet continues to be developed with new modules added to exploit vulnerabilities in Linux devices. A recent campaign targets DVR devices with remote code execution vulnerabilities and uses a domain generation algorithm to generate domains for C2 communication. Upon successful remote code execution, the devices are made part of the botnet and an XMRig crypto miner is installed. Other functionality of the current botnet includes a network sniffer, brute-force functionality, installation of Windows rootkits and infecting HTML, JS, PHP files.
The McAfee Enterprise ATR Team gathers and analyzes information from multiple open and closed sources before disseminating intelligence reports.
This campaign was researched by Juniper Threat Labs and shared publicly here.
How to use this article:
- If a Threat Hunting table has been created, use the rules contained to search for malware related to this campaign.
- Review the product detection table and confirm that your environment is at least on the specified content version.
To download the latest content versions, go to the Security Updates page.
- Scroll down and review the "Product Countermeasures" section of this article. Consider implementing them if they are not already in place.
- Review KB91836 - Countermeasures for entry vector threats, which contains countermeasures.
- Review KB87843 - List of and best practices for Endpoint Security Dynamic Application Containment rules.
- Review KB82925 - Identify what rule corresponds to an Adaptive Threat Protection and Threat Intelligence Exchange event.
This Knowledge Base article discusses a specific threat that is being tracked. The list of IOCs will change over time; check MVISION Insights for the latest IOCs.
Campaign IOC
| Type |
Value |
| SHA256 |
EB4A48A32AF138E9444F87C4706E5C03D8DC313FABB7EA88C733EF1BE9372899 |
| SHA256 |
F72BABF978D8B86A75E3B34F59D4FC6464DC988720D1574A781347896C2989C7 |
| SHA256 |
0E537DB39A7BE5493750B7805E3A97DA9E6DD78A0C7FCA282A55A0241803D803 |
| SHA256 |
E524BD7789B82DF11891CC2C12AF1AC0EA41DD0B946E1E04A4246CB36321F82F |
| DOMAIN |
gtmpbeaxruxy.myftp.org |
| URL |
http://gtmpbeaxruxy.myftp.org/setup.py |
| URL |
http://gtmpbeaxruxy.myftp.org/setup |
| URL |
http://gtmpbeaxruxy.myftp.org/xmrig |
| URL |
http://gtmpbeaxruxy.myftp.org/xmrig1 |
| IP-DST |
85.159.44.163 |
Minimum Content Versions:
| Content Type |
Version |
| V2 DAT (VirusScan Enterprise) |
10162 |
| V3 DAT (Endpoint Security) |
4614 |
Detection Summary
| IOC |
Scanner |
Detection |
| EB4A48A32AF138E9444F87C4706E5C03D8DC313FABB7EA88C733EF1BE9372899 |
AVEngine V2 |
Linux/SpyBot |
| AVEngine V3 |
Linux/SpyBot |
| JTI (ATP Rules) |
- |
| RP Static |
- |
| RP Dynamic |
- |
| IOC |
Scanner |
Detection |
| F72BABF978D8B86A75E3B34F59D4FC6464DC988720D1574A781347896C2989C7 |
AVEngine V2 |
PUP-XNS-AN |
| AVEngine V3 |
PUP-XNS-AN |
| JTI (ATP Rules) |
- |
| RP Static |
- |
| RP Dynamic |
- |
| IOC |
Scanner |
Detection |
| 0E537DB39A7BE5493750B7805E3A97DA9E6DD78A0C7FCA282A55A0241803D803 |
AVEngine V2 |
LINUX/Coinminer.az |
| AVEngine V3 |
LINUX/Coinminer.az |
| JTI (ATP Rules) |
- |
| RP Static |
- |
| RP Dynamic |
- |
| IOC |
Scanner |
Detection |
| E524BD7789B82DF11891CC2C12AF1AC0EA41DD0B946E1E04A4246CB36321F82F |
AVEngine V2 |
PY/Spybot.gen.a |
| AVEngine V3 |
PY/Spybot.gen.a |
| JTI (ATP Rules) |
- |
| RP Static |
- |
| RP Dynamic |
- |
Aggressive set of Manual Rules to improve protection to block this campaign
IMPORTANT: Always follow best practices when you enable new rules and signatures.
When you implement new rules or signatures, always set them to Report mode first and check the alerts generated. Resolve any issues that arise and then set the rules to Block. This step mitigates against triggering false positives and allows you to refine your configuration.
For more information, see KB87843 - List of and best practices for Endpoint Security Dynamic Application Containment rules.
Virusscan Enterprise - Access Protection Rules:
Prevent creation of new executable files in the Windows folder
Prevent programs registering as a service
Host Intrusion Prevention:
Rule ID: 1020 Windows Agent Shielding - File Access
Rule ID: 1148 CMD Tool Access by a Network Aware Application
Rule ID: 6011 Generic Application Invocation Protection
Rule ID: 6010 Generic Application Hooking Protection
Rule ID: 2806 Attempt to create a hardlink to a file
|
