Vulnerability StyleSmuggler: zero-day attack on Magento and Adobe Commerce
Backdoor Rust-based and communications disguised as NTP: what to know and how to defend yourself

KEY TAKEAWAYS
- StyleSmuggler is a zero-day vulnerability affecting all versions of Magento and Adobe Commerce, exploited to install a Rust-based backdoor.
- The attack exploits Magento's template system to execute malicious code and create fake 'payment failed' emails, with communications disguised as Network Time Protocol (NTP).
- Adobe is working on a patch, expected for September 8, but in the meantime, it is advised to disable GraphQL as a mitigating measure.
- Administrators should monitor suspicious 'Payment Transaction Failed Reminder' emails, processes like 'kworker' or 'fc-cache', suspicious cron entries, and temporary files.
- In case of suspected compromise, it is crucial to rotate Magento credentials to prevent further damage.
Zero-day "StyleSmuggler" exploits Magento and Adobe Commerce to install backdoors
A zero-day vulnerability named "StyleSmuggler" affects all versions of Magento and Adobe Commerce, allowing attackers to install a backdoor. The first documented attack occurred on September 4 on a system updated with the latest security patches. The e-commerce security company Sansec has confirmed that Adobe Enterprise Support is working on a fix, but has not provided a specific timeline for its release.
Quick Response
What is the StyleSmuggler zero-day?
A zero-day vulnerability affecting all versions of Magento and Adobe Commerce, exploited to install a Rust-based backdoor. It also affects systems updated with the latest patches.
How does the attack work?
- Abuses Magento's template system through PHP code injection
- Generates fake "payment failed" emails to execute code
- Installs a backdoor that disguises itself as a legitimate process
- Sets up a cron job for persistence
What are the signs of compromise?
- Unexpected increase in "Payment Transaction Failed Reminder" emails
- Suspicious processes like 'kworker' or 'fc-cache'
- Suspicious cron entries and temporary files
Magento, Adobe's open-source e-commerce platform, is installed on over 160,000 websites, including 14,000 among the top one million most visited sites. The exploitation observed by Sansec abuses Magento's template system through PHP code injection to generate a fake "payment failed" email, which in turn triggers code execution.
The successful exploitation installs a small Rust-based backdoor as a background process, disguised as [kworker/u:8:0]. In newer versions, the process is masked as fc-cache and copied to ~/.cache/fontconfig/fc-cache. Sansec researchers noted that the attacker also adds a cron job configured to repeat every 30 minutes, ensuring malware persistence.
Although Sansec has not observed subsequent activity, the malware is capable of communicating with remote infrastructures and receiving commands. Researchers observed that previous samples of the backdoor used TLS/WebSockets to communicate with the command-and-control (C2) address, while newer versions mask traffic as Network Time Protocol (NTP).
The malware sends UDP packets to port 123 and uses hostnames that resemble time synchronization infrastructures, helping to disguise malicious traffic as NTP and allowing it to bypass firewalls. Additionally, the malware determines the server's public IP using services like ipify, icanhazip, ident.me, and ipinfo.io, and checks Linux's TracerPid value to detect tracing. If tracing is active, the malware does not send presence signals but is still installed.
Indicators of Compromise and Recommendations
Sansec reports that an unexpected increase in Magento's "Payment Transaction Failed Reminder" emails may indicate exploitation. The company also recommends monitoring 'kworker' or 'fc-cache' processes, suspicious cron entries, and temporary files. In case of suspected compromise, it is advised to rotate Magento credentials.
As of writing, Adobe has not released fixes for StyleSmuggler, but the next security release is scheduled for September 8. Until fixes are available, Sansec advises site administrators to disable GraphQL as a mitigation measure. BleepingComputer contacted Adobe to ask if a fix for StyleSmuggler is planned for tomorrow's release, but the company has not yet responded.
Effectively managing a zero-day vulnerability like StyleSmuggler requires a proactive approach to cybersecurity. This includes adopting Managed Detection and Response (MDR) solutions for timely attack detection and considering a cyber risk policy to mitigate potential financial damages.
Additionally, it is crucial to maintain NIS2 compliance and DORA, as well as implement ransomware protection measures to ensure operational resilience. Investing in a managed Security Operations Center can also improve incident response capabilities and vulnerability management.
The StyleSmuggler vulnerability underscores the importance of a multi-layered approach to security, which includes not only timely security patches but also advanced Data Loss Prevention solutions and zero trust architecture. These tools can help prevent unauthorized access and protect sensitive data even in the presence of known vulnerabilities.
Impact on the e-commerce market and future prospects
The discovery of StyleSmuggler comes at a critical time for the e-commerce sector, which has seen a record increase in cyberattacks during the summer months. According to data from Sansec, attacks on e-commerce platforms have increased by 43% compared to the previous year, with a significant peak in the July-August period. The vulnerability particularly affects SMEs using Magento, often with limited cybersecurity resources.
Implications for compliance and risk management
For companies subject to NIS2 and DORA, StyleSmuggler represents another piece in the complex regulatory landscape. Auditors are already reporting that this vulnerability could be considered an indicator of non-compliance, especially for organizations that have not implemented timely mitigation measures. The NIS2 directive indeed requires proactive vulnerability management, with particular attention to zero-days.
Alternative technical solutions
In the absence of official patches, some security experts suggest implementing advanced Data Loss Prevention solutions to monitor suspicious traffic. Tools such as WAFs (Web Application Firewalls) configured to block anomalous requests to Magento's template system could offer temporary protection. Additionally, adopting zero trust architecture could limit the impact of potential compromises by segmenting access to critical resources.
Future predictions
Experts predict that once the patch is released, attackers will focus on other similar vulnerabilities, exploiting Magento's extensive ecosystem of extensions. This scenario requires a continuous approach to security, with the adoption of SOC as a Service for constant monitoring of infrastructures. Furthermore, the increasing complexity of attacks underscores the importance of investing in MDR for a timely and effective incident response.
Final considerations
StyleSmuggler represents a case study on the evolution of threats in the e-commerce sector. The combination of advanced evasion techniques and the use of modern languages like Rust indicates a concerning trend towards more sophisticated attacks. For organizations, the key lesson is the importance of a multi-layered approach to security, which integrates technology, processes, and continuous staff training. Only through a layered defense will it be possible to withstand emerging threats in an ever-evolving landscape.
Frequently Asked Questions
What is the financial impact of a StyleSmuggler attack?
The financial impact can be significant, with costs ranging from tens of thousands to millions of euros depending on the size of the organization. This includes direct losses, malware removal costs, possible fines for non-compliance with regulations, and reputational damage.
How can I verify if my site has been compromised?
In addition to the already mentioned signs of compromise, it is possible to use forensic analysis tools to examine server logs and identify suspicious activities. Collaboration with cybersecurity experts can provide a more accurate assessment of the system's status.
What are the alternatives to Magento in case of persistent vulnerabilities?
Some alternatives include Shopify Plus for companies looking for a fully managed solution, or open-source platforms like WooCommerce with a more customizable approach. However, it is crucial to carefully evaluate the organization's specific needs and conduct a thorough risk analysis.
Editorial Note and Disclaimer
The guides and content published on GoYou are the result of independent research and analysis activities, for informational, educational, and in-depth purposes.
GoYou does not constitute a journalistic publication nor an editorial product pursuant to Law No. 62/2001 and does not provide real-time information.
The GoYou project does not provide professional, technical, legal, or financial advice and disclaims all responsibility for the improper use of the information published.
In the Crypto sector, every investment involves risks: readers are invited to always inform themselves independently before making any decision.
Source: bleepingcomputer.com · GoYou.it is not a registered news outlet; all content is for informational and educational purposes.