Dell Shipped Malware Infected Motherboards
W32.Spybot worm discovered in flash memory on some replacement PowerEdge server motherboards.
![](https://eu-images.contentstack.com/v3/assets/blt6d90778a997de1cd/bltc94608acf452fd67/655cf371ab171e040a838b2a/329050_DR23_Graphics_Website_V5_Default_Image_v1.png?width=1280&auto=webp&quality=95&format=jpg&disable=upscale)
Dell has inadvertently shipped replacement motherboards for its PowerEdge servers that are infected with the Spybot worm. The malware affects servers running Windows, but not other operating systems.
The worm can be triggered if users run an update to either the Unified Server Configurator (USC) or 32-bit Diagnostics on the server.
According to a Dell employee posting to the PowerEdge server support forum, "the W32.Spybot worm was discovered in flash storage on the motherboard during Dell testing." The worm, which is not part of the firmware, can be blocked by "all industry-standard antivirus programs on the market today," he said.
The employee offered more details about the extent of the infection: "This issue does not affect any Dell PowerEdge servers shipped from our factories and is limited to a small number of the replacement motherboards only which were sent via Dell's service and replacement process for four servers: PowerEdge R310, PowerEdge R410, PowerEdge R510, and PowerEdge T410."
Fewer than 1% of each of the server models were potentially exposed to the malware, according to Dell, and affected motherboards are no longer being shipped. In addition, PowerEdge servers containing an Integrated Dell Remote Access Controller (iDRAC) Express or iDRAC Enterprise card are not affected.
Dell is calling affected customers directly to schedule a visit from a technician to replace the affected motherboards. The company said that "to date, we have received no customer reports related to data security" for the servers containing the malware.
But one Dell customer, posting to the PowerEdge support forum, faulted the company for warning customers about the issue, but not providing full technical details or an online recall notice with full vulnerability information, "especially when they asked to be able to schedule the service call to resolve the issue at least 10 business days in the future."
About the Author
You May Also Like
Catch the Threat Before it Catches you: Proactive Ransomware Defense
September 5, 2024How to Evaluate Hybrid-Cloud Network Policies and Enhance Security
September 18, 2024DORA and PCI DSS 4.0: Scale Your Mainframe Security Strategy Among Evolving Regulations
September 26, 2024Harnessing the Power of Automation to Boost Enterprise Cybersecurity
October 3, 2024
[Virtual Event] The Essential Guide to Cloud Management
October 17, 2024Black Hat Europe - December 9-12 - Learn More
December 10, 2024SecTor - Canada's IT Security Conference Oct 22-24 - Learn More
October 22, 2024