The Splunk Threat Research Team is monitoring several malicious payloads targeting Customer Premise Equipment (CPE) devices. These are defined as devices that are at customer (Commercial, Residential) premises and that provide connectivity and services to the internet backbone. Examples include:
The above devices are prevalent and fundamental for internet connectivity. Malicious actors can target these devices to build very powerful botnets which in combination with tactical payloads, can potentially exert a significant effect on critical internet infrastructure or even Operational Technologies devices. CPE devices are generally not very powerful in terms of processing or functionality, however, when hundreds of thousands of these devices are compromised and work in aggregation via Command and Control they can cause significant damage. An example of this type of payload is VPNFilter discovered by Cisco Talos and said to have compromised 500,000 devices worldwide.
Based on the current, ongoing geopolitical events and the recent takedown of a similar malicious payload by the FBI named “Cyclops Blink” and attributed to Russian Federation’s Main Intelligence Directorate (GRU). The Splunk Threat Research Team has developed specific analytics to detect this type of malicious code, including Cyclops Blink, and AcidRain.
The main malicious functions of these malicious payloads can be resumed in:
Another common thing about these payloads is that they target popular commercial CPE brands. This speaks of the intention of targeting critical infrastructure to gain access, implant malicious payloads, and hoard as many compromised devices as possible that can be used for subsequent attacks.
Due to the ability to download additional payloads, these additional payloads may likely be implemented based on tactical objectives (DDoS, Destruction, Corporate Espionage, Lateral Movement, etc). It is important to notice that many of these devices are not just commercial, industrial, or military but used in civilian networks, which exposes the general population to these attacks and presents a direct threat to civilian infrastructure and livelihood.
For specific make and model of affected devices please refer to the reference section at the end of this advisory.
The following are the detections crafted for these payloads.
Name | Technique ID | Tactic | Description |
Linux Iptables Firewall Modification | Defense Evasion | This analytic looks for suspicious command lines that modify the iptables firewall setting of a Linux machine. | |
Linux Kworker Process CommandLine | Defense Evasion | This analytic looks for suspicious process kworker command lines in a Linux machine. | |
Linux Stdout Redirection To Dev Null File | Defense Evasion | This analytic looks for suspicious command lines that redirect the stdout or possible stderr to dev/null file. |
Name | Technique ID | Tactic | Description |
Linux High Frequency Of File Deletion In Etc Folder(New) | Defense Evasion, Impact | This analytic looks for a high frequency of file deletion relative to process name and process id /etc/ folder. | |
Linux Deletion Of Init Daemon Script(New) | Defense Evasion, Impact | This analytic looks for deletion of the init daemon script in a Linux machine. | |
Linux Deletion of SSL Certificate(New) | Defense Evasion, Impact | This analytic looks for deletion of the SSL certificate in a Linux machine. | |
Linux deletion Of SSH Key(New) | Defense Evasion, Impact | This analytic looks for deletion of an ssh key in a Linux machine. | |
Linux Deletion Of Services(New) | Defense Evasion, Impact | This analytic looks for deletion of services in a Linux machine. | |
Linux Deletion Of Cron Jobs(New) | Defense Evasion, Impact | This analytic looks for deletion of cron jobs in a Linux machine. |
The above searches will be available at research.splunk.com, the Splunk Threat Research Team (STRT) security content repository, and the Splunk ES Content Update (ESCU) application at Splunkbase.
Filename | Size | Sha256 |
acid_rain.elf | 22656 bytes (22 KiB) | 9b4dfaca873961174ba935fddaf696145afe7bbf5734509f95feb54f3584fd9a |
cyclopblink1 | 2332316 bytes (2277 KiB) | 4ec5e0c5dccc5891d39ea76e3c3d3e26d8830d7aa4d63db6084dbfbec6f0d211 |
cyclopblink2 | 7346456 bytes (7174 KiB) | fc1e50172c0ce221452b967d1ef705f11bbfe2d54c533d68bd2a7a094605df2d |
The above detections were crafted under a Linux environment and can be used as guidelines for other architectures such as MISP or PowerPC. The key to implementing these types of detections is the ability to monitor via a logging mechanism (i.e syslog).
Addressing the threat of these types of payloads can be very difficult as many of these devices do not allow for the implementation of centralized logging which impairs monitoring and defense. Considering that many enterprises have had remote work programs since the pandemic started, their perimeter may likely have a device affected by these payloads, in which case the best course of action is to disconnect, discard and replace them. Some other mitigation options are:
It is also important to consider that an advanced adversary as the aforementioned has likely devised other ways of access, exploitation or persistence that may be yet unknown and that may target these devices after remediation. This is why prevention, monitoring, and detection are fundamental to defend against these threats.
You can find the latest content about security analytic stories on GitHub and in Splunkbase. Splunk Security Essentials also has all these detections available via push update. In the upcoming weeks, the Splunk Threat Research Team will be releasing a more detailed blog post on this analytic story. Stay tuned!
For a full list of security content, check out the release notes on Splunk Docs.
Any feedback or requests? Feel free to put in an issue on GitHub and we’ll follow up. Alternatively, join us on the Slack channel #security-research. Follow these instructions If you need an invitation to our Splunk user groups on Slack.
We would like to thank the following for their contributions to this post.
The Splunk platform removes the barriers between data and action, empowering observability, IT and security teams to ensure their organizations are secure, resilient and innovative.
Founded in 2003, Splunk is a global company — with over 7,500 employees, Splunkers have received over 1,020 patents to date and availability in 21 regions around the world — and offers an open, extensible data platform that supports shared data across any environment so that all teams in an organization can get end-to-end visibility, with context, for every interaction and business process. Build a strong data foundation with Splunk.