Overview for rules released by Trustwave SpiderLabs in this month for ModSecurity Commercial Rules package. The rules available to versions 2.9.x and 3.x of ModSecurity. Those rules are developed to detect attacks or classes of attacks on web applications and their components as well as to provide virtual patches for public vulnerabilities.
Release Summary
Trustwave SpiderLabs also released 17 new rules to detect suspicious crypto-mining and magecart activity.
Although crypto-mining can be done legitimately, when website owners deploy mining software as an alternative to advertisements, the inserted code is mostly used by hackers as malware to hijack and utilize the CPU power of website visitors to their own advantage.
In these cases, the presence of crypto-mining script is clear evidence that the website has been compromised.
This release also includes a set of rules tailored to alert and deny attempts to exploit vulnerable Magento installations and also detecting and blocking scripts that have been infected/compromised by Magecart actors or attacks that resembles this modus operandi. For more information regarding Magecart and these rules, please refer to “Magecart - An overview and defense mechanisms” on the Trustwave blog.
Please note that the default action for the Crypto-Mining Activity rules is LOG only and further action needs to be taken if your website has already been compromised:
For more information regarding crypto-mining, please refer to the Trustwave blog.
How to Update
All the rules released this month are already available for download and can be configured on the ModSecurity Dashboard. The rules are associated with the default profile and enabled for all licensed servers. In order to verify the rules were successfully downloaded by ModSecurity, login to ModSecurity Dashboard and verify the server "Last seen" date, which indicates the last successful download for the specified server.