BLOG

F5 Malware Analysis: Slave

Lori MacVittie 축소판
Lori MacVittie
Published July 02, 2015

Malware. It’s come to be a significant factor in attacks against both corporate and consumer assets. It continues to result in millions of dollars in fraud while simultaneously chipping away at consumer trust in financial and banking institutions.

Research indicates that preventing and/or detecting malware threats is a top factor driving network security strategy today. Given that Google found just this year that a primary delivery mechanism for malware, phishing, still catches nearly half of its targets that’s no surprise.

It behooves us, then, as leaders and practitioners interested in addressing these issues to be aware of new and rising malware threats that may compromise both our systems and the systems of our consumer-customers. 

One such rising dark star is “Slave.” First spotted in March 2015, Slave targets banking web apps with script injections designed to perform a number of functions including credential theft, account access and automatic funds transfers.

In many respects Slave is less sophisticated than some of its cousins, but that makes it no less dangerous. To help you better understand the threat – and defend against it – our security researchers have put together a detailed analysis of this pernicious piece of software and made it available on DevCentral.

Stay safe out there!

malware-factors

why malware matters

###

Editors Note: F5 and DevCentral do not condone the usage of the term ‘slave’ in the context of our technology. In this case the term ‘slave’ is a name, used to specify a particular piece of malware. We believe removing or changing the term, here, would only cause confusion and remove information necessary for effective application security.