Attacks/Breaches

11/24/2015
12:15 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Stealthy ModPOS Is 'Most Sophisticated PoS Malware' Ever

More than just a point-of-sale card scraper, it's modular malware, and every module is a rootkit.

Just in time for the holidays, researchers at iSIGHT Partners are warning retailers about ModPOS -- malware in their point-of-sale systems that is nearly impossible to detect, can do a whole lot more than just scrape customers' credit card data, and has already successfully breached U.S. retailers.

"This is by far the most sophisticated PoS malware I've ever seen," says Maria Noboa, senior threat analyst at iSight.

BlackPOS was behind the monster breach at Target, BackOff hit UPS and over a thousand others, and now new PoS malware like CherryPicker and AbaddonPOS have hit the scene. Yet, none of them have the same level of complexity and committment to stealth that ModPOS does.

"It took us two to three weeks just to determine it was malicious," says Noboa. It then took researchers several more weeks to pick ModPOS apart and figure out how it works. In comparison, it only took them about 20 minutes to reverse engineer CherryPicker, says Noboa.

[PoS malware proves that Cyber Monday isn't the only thing retailers and shoppers have to worry about over the holidays. Read "Black Friday Security: Brick-and-Mortar Retailers Have Cyber Threats Too."]

ModPOS is modular. In addition to the PoS card scraper module, it also has a keylogger, an uploader/downloader (with which it could add other pieces), and plug-ins for scraping credentials, and gathering local system and network information.

So, explains Noboa, if it compromises the point-of-sale system and finds that the retailer has wisely encrypted all of the cardholder data or stored it elsewhere, ModPOS can still find ways to make its attack fruitful for them and damaging to the target.

The code was written by someone with exceptional skill, says Noboa. "The shell code they use," she says, "are effectively full programs." They found one piece of shell code contained over 600 functions.

The malware is able to stay persistent and obfuscated because every one of those modules operates in kernel mode, so, "each one is a rootkit," says Noboa.

It's also difficult to detect because all hashes are unique to the victim system. So the researchers can't just hand out a list of hashes along with indicators of compromise, because it wouldn't do anybody any good.

The researchers have not found any evidence of anyone selling ModPOS or even discussing it on underground forums. 

"All of this points to [the malware] being a profit center for someone," says Noboa. They're making their money from use of the malware, not sale of it, and they're not interested in sharing.

All of this has helped ModPOS be quietly lucrative. iSight researchers believe the ModPOS attacks began as early as 2013, and have since stolen millions of credit and debit cards from unnamed U.S. retailers.

They don't know yet how it's being distributed right now or have a fix on the threat actor. They do say there are indications that point to Eastern Europe.

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
What We Talk About When We Talk About Risk
Jack Jones, Chairman, FAIR Institute,  7/11/2018
Ticketmaster Breach Part of Massive Payment Card Hacking Campaign
Jai Vijayan, Freelance writer,  7/10/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14084
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for MKCB, an Ethereum token. If the owner sets the value of sellPrice to a large number in setPrices() then the "amount * sellPrice" will cause an integer overflow in sell().
CVE-2018-14085
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for UserWallet 0x0a7bca9FB7AfF26c6ED8029BB6f0F5D291587c42, an Ethereum token. First, suppose that the owner adds the evil contract address to his sweepers. The evil contract looks like this: contract Exploit { uint public start; function swe...
CVE-2018-14086
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for SingaporeCoinOrigin (SCO), an Ethereum token. The contract has an integer overflow. If the owner sets the value of sellPrice to a large number in setPrices() then the "amount * sellPrice" will cause an integer overflow in sell(...
CVE-2018-14087
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for EUC (EUC), an Ethereum token. The contract has an integer overflow. If the owner sets the value of buyPrice to a large number in setPrices() then the "msg.value * buyPrice" will cause an integer overflow in the fallback functio...
CVE-2018-14088
PUBLISHED: 2018-07-16
An issue was discovered in a smart contract implementation for STeX White List (STE(WL)), an Ethereum token. The contract has an integer overflow. If the owner sets the value of amount to a large number then the "amount * 1000000000000000" will cause an integer overflow in withdrawToFounde...