<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Javascript-Skimmer on CuraSec</title><link>https://curasec.metacog.co.kr/tags/javascript-skimmer/</link><description>Recent content in Javascript-Skimmer on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 27 Oct 2026 16:34:51 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/javascript-skimmer/index.xml" rel="self" type="application/rss+xml"/><item><title>953 Magento Stores Hit by Scanner-Evading JavaScript Skimmer Campaign</title><link>https://curasec.metacog.co.kr/insights/2026-10-27-hackers-infect-953-online-stores-with-scanner-evading-javasc/</link><pubDate>Tue, 27 Oct 2026 16:34:51 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-27-hackers-infect-953-online-stores-with-scanner-evading-javasc/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> If you run Magento, audit all CMS blocks for unauthorized JavaScript snippets and review admin access logs for changes since July 2025; confirm no rogue loader code is being served to shoppers from page templates.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> Build or tune detections for unexpected CMS block modifications and scanner-evading JavaScript loader injections in web application logs; consider hunting for this pattern in any Magento estate back to July 2025.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A long-running skimmer campaign touching nearly a thousand stores is a useful risk-register input for any organization running Magento e-commerce; relevant to PCI DSS scope reviews but not a board-level systemic event today.&lt;/li>
&lt;/ul></description></item></channel></rss>