Tupperware Site Hacked With Credit Card Skimmer

Tupperware hasn’t yet put a lid on a targeted cyberattack that uses a credit card skimmer to collect customer payment information at checkout on the tupperware[.]com site and some of its local sites.

The threat actors hid “malicious code within an image file that activates a fraudulent payment form during the checkout process,” according to researchers at Malwarebytes who discovered the compromise March 20. “This form collects customer payment data via a digital credit card skimmer and passes it on to the cybercriminals with Tupperware shoppers none-the-wiser.”

The Tupperware party long ago moved to the internet – with more than one million people visiting the company’s website monthly. And as COVID-19 virus drives more people online to shop, the researchers wrote in a Wednesday blog post that “there is little doubt that a larger number of transactions will be impacted by credit card skimmers,” one of the top web threats they monitor.

The actors behind the Tupperware compromise put effort behind integrating the skimmer seamlessly and remain undetected. Malwarebytes found the malicious activity during a web crawl after coming across a suspicious iframe loaded from deskofhelp[.]com when visiting the retailer’s checkout page and which displays the payment form fields used by shoppers.   

The domain was registered on March 9 using an email address with Russian provider Yandex and found alongside other phishing domains.

The hackers’ scheme weren’t meticulous, though. “The attackers didn’t carefully consider (or perhaps didn’t care about) how the malicious form should look on localized pages,” the researchers wrote, noting that while the Spanish version of the Tupperware site is written in Spanish, the rogue payment form remained in English.

Malwarebytes notified Tupperware of its findings but the skimmer was still active when the company published its findings today.

“Typically, when it comes to a website hack, an organization needs to react fast and either temporarily disable their site or quickly remove the offending code,” Jerome Segura, director of threat intelligence, Malwarebytes Labs told SC Media.

But the security challenge doesn’t stop there. “Attackers can return hours later and place new code,” said Segura.

Site owners should perform a full security sweep to identify the root cause and tease out backdoors and other artifacts. Breaches often occur because a vulnerability is left unpatched.  But “due to the nature of content management systems and their plugins, the patching process is not always straightforward,” said Segura.

“Most e-commerce companies should have a security contact form or better, a security.txt file, on their site,” he said. “This makes reporting breaches easier and ensures that the time to remediate is as short as possible.”