eCommerce servers are being targeted with remote access malware that hides on Nginx servers in a way that makes it virtually invisible to security solutions. “NginRAT essentially hijacks a host Nginx application to stay undetected. To do that, NginRAT modifies core functionality of the Linux host system. When the legitimate Nginx web server uses such functionality (eg dlopen), NginRAT intercepts it to inject itself.” . The threat received the name NginRAT, a combination of the application it targets and the remote access capabilities it provides and is being used in server-side attacks to steal payment card data from online stores. NginRAT was found on eCommerce servers in North America and Europe that had been infected with CronRAT , a remote access trojan (RAT) that hides payloads in tasks scheduled to execute on an invalid day of the calendar. . NginRAT infiltrates online retail platforms by masquerading as a genuine nginx operation, presenting a significant cybersecurity challenge to digital marketplaces.. NginRAT, eCommerce Security, Malware Threats, Remote Access Trojans, Nginx Servers. . LinuxSecurity.com Team
Rootkit.Linux.Snakso.a is designed to infect the Linux kernel version 2.6.32-5-amd64 and adds an iframe to all served web pages by the infected Linux server via the nginx proxy. . The malware appears to be in its development stages as the code is rather large (more than 500k, including debugging information) and Kaspersky noted that "some of the functions don The link for this article located at Toms Hardware is no longer available. . The malware appears to be in its development stages as the code is rather large (more than 500k, inc. linux, rootkit, snakso, designed, infect, kernel, version, 32-5-amd64. . LinuxSecurity.com Team
Several days ago, I had to deal with a compromised web application: an attacker had somehow managed to upload PHP backdoor scripts onto the application. As I researched the vulnerability a bit more, however, I realized that many of the nginx / PHP setup tutorials found on the Internet suggest that people use vulnerable configurations. The misconfiguration As I mentioned, the attack was made possible by a very simple misconfiguration between nginx and php-fastcgi. Consider the configuration block below, taken from a tutorial at https://www.linode.com/docs/guides/nginx-and-phpfastcgi-on-fedora-14/ The link for this article located at NealPoole is no longer available. . As I researched the vulnerability a bit more, however, I realized that many of the nginx / PHP setup. compromised, application, attacker, somehow, managed. . LinuxSecurity.com Team
Get the latest Linux and open source security news straight to your inbox.