Home Cyber Attack Magecart Skimmer Attacks Sites Whilst Hiding Stolen Data In JPG Files

Magecart Skimmer Attacks Sites Whilst Hiding Stolen Data In JPG Files

by Abeerah Hashim
Magecart hiding PHP web shells in favicons

Continuing with their invasive strategies, the e-commerce predator Magecart has developed another malicious feature. As observed, the latest Magecart skimmer evades detection by hiding stolen data in JPG image files.

Magecart Hiding Stolen Data In JPG Files

Researchers from Sucuri have observed new Magecart skimmer that has adopted a new evasive strategy.

As elaborated in their post, they found Magecart skimmer active on Magento 2 websites hiding stolen data in JPG files. The researchers noticed the malicious code injected into the checkout page where it captured POST request data from the customers. The same code also created .jpg files to which it then stored the stolen information.

The… PHP code was found injected to the file ./vendor/magento/module-customer/Model/Session.php. To load the rest of the malicious code onto the compromised environment, the getAuthenticates function is created and called.
The code also creates the image file (pub/media/tmp/design/file/default_luma_logo.jpg), which it uses to store any captured data.

In this way, the malware strived to stay under the radar. Whereas, it also gave the attackers the convenience of downloading the stolen information whenever feasible.

As for the target details, the malware steals almost every detail that a user provides on the checkout page. This includes customers’ names, complete addresses, payment card details, phone numbers, and user agent details.

Any Mitigations?

The recent Magecart attack strategy looks pretty sneaky and different to grab attention.

Given that it’s active in the wild, website owners, particularly, the owners of online stores, need to remain vigilant for website security. Otherwise, the existence of such skimmers on their sites will not only harm their customers but will also ruin the store’s reputation.

Despite being sneaky, it isn’t entirely impossible to spot though. According to the researchers, the site owners should employ integrity control checks and website monitoring services to detect malicious changes.

Let us know your thoughts in the comments

You may also like

Latest Hacking News

Privacy Preference Center


The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis.

cookie_notice_accepted and gdpr[allowed_cookies] are used to identify the choices made from the user regarding cookie consent.

For example, if a visitor is in a coffee shop where there may be several infected machines, but the specific visitor's machine is trusted (for example, because they completed a challenge within your Challenge Passage period), the cookie allows Cloudflare to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does not store any personally identifiable information.

__cfduid, cookie_notice_accepted, gdpr[allowed_cookies]


DoubleClick by Google refers to the DoubleClick Digital Marketing platform which is a separate division within Google. This is Google’s most advanced advertising tools set, which includes five interconnected platform components.

DoubleClick Campaign Manager: the ad-serving platform, called an Ad Server, that delivers ads to your customers and measures all online advertising, even across screens and channels.

DoubleClick Bid Manager – the programmatic bidding platform for bidding on high-quality ad inventory from more than 47 ad marketplaces including Google Display Network.

DoubleClick Ad Exchange: the world’s largest ad marketplace for purchasing display, video, mobile, Search and even Facebook inventory.

DoubleClick Search: is more powerful than AdWords and used for purchasing search ads across Google, Yahoo, and Bing.

DoubleClick Creative Solutions: for designing, delivering and measuring rich media (video) ads, interactive and expandable ads.



The _ga is asssociated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners.

The _gat global object is used to create and retrieve tracker objects, from which all other methods are invoked. Therefore the methods in this list should be run only off a tracker object created using the _gat global variable. All other methods should be called using the _gaq global object for asynchronous tracking.

_gid works as a user navigates between web pages, they can use the gtag.js tagging library to record information about the page the user has seen (for example, the page's URL) in Google Analytics. The gtag.js tagging library uses HTTP Cookies to "remember" the user's previous interactions with the web pages.

_ga, _gat, _gid