/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Researchers say that attackers have been bypassing e-commerce sites' Content Security Policy with a method using Google Analytics API, to scrape payment info

Sergiu Gatlan / BleepingComputer :

BleepingComputer Sergiu Gatlan

Context & Ripple Effects

E-commerce skimming research has spent years circling the same target: checkout pages protected only by browser policy. Researchers demoed HEIST in 2016, showing sensitive data could be lifted from HTTPS pages without a man-in-the-middle position, and an unauthenticated Magento exploit in 2019 put hundreds of thousands of stores at risk from the server side.

First-order effects

  • Merchants that deployed Content Security Policy as their primary anti-skimming defense lose that control's value wherever the Google Analytics API sits on their allowlist, since attackers can now route stolen payment data through a domain every store already trusts.
  • Security teams at online retailers face immediate re-audit work: any third-party script whitelisted on a checkout page is now a potential exfiltration channel, not just a functional dependency.

Second-order effects

  • Google comes under pressure to police how its own measurement API is weaponized, echoing its later downplaying of malware that abused an undocumented Chrome API for token theft — platform owners increasingly cast as unwilling accomplices in browser-based attacks.
  • The breach economics favor groups like Keeper, which had already hit at least 570 e-commerce portals by mid-2020 with Magento sites as the dominant victims; a CSP bypass lowers the cost of scaling card-skimming across those same soft targets.

Third-order effects

  • If attackers keep laundering theft through whitelisted first-party-adjacent services, the industry drifts away from domain-allowlist security models entirely, toward integrity-checked scripts and hardware-bound payment fields on checkout pages.
  • Stolen card data feeds a maturing monetization pipeline downstream, as later investigations show phished card numbers being converted into mobile wallets for online and in-store spending — meaning each skimmed checkout now has a ready cash-out path.

The trend: Web payment skimming is shifting from breaking into servers to abusing the trusted third-party scripts merchants themselves invite onto checkout pages.

Discussion

  • @adam_k_levin Adam Levin on x
    Hackers are using Google's servers and the Google Analytics platform to steal credit card information submitted by customers of online stores. https://www.bleepingcomputer.com/ ...
  • @glenngabe Glenn Gabe on x
    Researchers say that attackers have been bypassing e-commerce sites' Content Security Policy w/a method using Google Analytics API to scrape payment info “The skimmer will monitor the site for user input & it will grab any entered credit card info” https://www.bleepingcomputer.co…