Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Threat Intelligence

12/18/2019
11:35 AM
50%
50%

Worried About Magecart? Here's How to Check for It

Researchers share how everyday users can check for malicious code on e-commerce websites.

Magecart mayhem has compromised online shoppers for years, and its activity has ramped up with attacks against Smith & Wesson, Macy's, and, most recently, Rooster Teeth. In a nutshell, attackers inject malicious code onto the checkout page of e-commerce platforms to lift payment data.

Normally, everyday consumers and small businesses learn about these incidents the hard way – after data has already been stolen. Security experts have advised the use of Content Security Policy (CSP) and Sub Resource Integrity (SRI) to prevent Magecart attacks. However, people and organizations with limited resources may not have the means to put these measures in place.

To give these users a Web security edge, Trustwave senior security researcher Michael Yuen today published a blog detailing how they can use a browser to check whether a shopping website is compromised. The process starts by accessing urlscan[.]io and running a public scan for the chosen site. Under "Domain & IP information," they can see IPs and domains of all requests performed on the site.

In an example, Yuen shows what it looks like when a request doesn't come from the same domain as the website, or from Facebook or Google. The "IP Detail" tab shows which domain the request is from; visitors also can see what is loaded on the site by clicking the HTTP tab located on top. When a script file is not loaded from the same domain as other script files, it's "a big red flag." Clicking "Show Response" reveals an obfuscated Magecart script in the suspicious domain.

Yuen also explains how users can look up the exfiltration URL to see where the exfiltrated data is being sent. Read more details in the full blog post here.

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "How to Manage API Security."

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-11844
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
CVE-2020-6937
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
CVE-2020-7648
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
CVE-2020-7650
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
CVE-2020-7654
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.