ProBackend
News & Analysis
3 weeks ago5 min read

Convertr Analytics Skimming: A Supply-Chain Card Heist Seen Through a Security & Compliance Analyst's Lens

Convertr Analytics Skimming: A Supply-Chain Card Heist Seen Through a Security & Compliance Analyst's Lens

A Brazilian Magecart group slipped a credit-card skimmer into Convertr's self-hosted Plausible analytics script, harvesting card numbers and CPF data across dozens of Brazilian fashion brands. Here is how it worked, how they likely got in, and what defenders should do now.

One Bad File, Hundreds of Stores, One Checkout Window

A single JavaScript file. That's all it took. Sometime around 22 October 2026, an attacker edited one script on a single analytics server, and from 24 October onward, every shopper checking out on any of the dozens of Brazilian fashion brands running on Convertr was quietly leaking their card number and their CPF tax ID to a domain called 1x0.is.

Convertr is the commerce backbone behind a large slice of Brazilian online fashion. By its own numbers, merchants have moved more than R$2 billion (roughly €320 million) through the platform. Every one of those stores loads a web-analytics tracker from analytics.convertr.app.br. The attacker didn't breach each store. They didn't have to. They poisoned the one file all of them trusted, and let the trust do the work for them.

For anyone working security & compliance, this is the case study you keep on file. It isn't exotic. It's a self-hosted analytics tool, an outdated version, and a skimmer bolted onto the end. The banality is the warning.

How the Skimmer Actually Worked

Convertr runs Plausible, an open-source alternative to Google Analytics, on its own server using the free Community Edition. The infected file, Sansec's forensics team wrote up in full, was the stock Plausible script with a malicious block appended to it. Clean on the surface. Poison underneath.

The logic was surgical. The script watched the page. A regex looked for checkout.convertr in the URL. No match, no action. The script stayed silent and looked like ordinary analytics. Only when a shopper landed on a genuine Convertr checkout page did the malware wake up.

Then it scraped three fields from the form: the card holder's name, the full card number, and the security code. It pushed all of it to 1x0.is, which also served as the command-and-control channel. Sansec's analysis notes that a Maltrail threat-intel feed had already flagged 1x0.is as malicious. So the exfil endpoint wasn't invisible. It just wasn't wired into anyone's detection path in time.

What strikes me as the most important detail here is also the least obvious one. The attacker didn't swap out the tracker. They kept the legitimate Plausible code intact and appended their payload to it. An analyst eyeballing the file would see a familiar analytics script and stop reading. The malware hid behind the credibility of the thing it was wearing.

The Way In: A Door Left Open on Purpose?

Sansec researchers believe the compromise is tied to the group's habit of scanning the internet for internet-facing applications running outdated versions. And Convertr's analytics server was, by that measure, outdated.

At the time of the incident, the latest Plausible Community Edition was version 2.2.0. The server was running 2.0.0, which shipped way back in February 2025. The version itself wasn't the vulnerability. The vector, per Sansec, was likely CVE-2026-8467, a flaw that allows unauthenticated access to the /storybook endpoint. It was published on 22 October, the same day Sansec reported first trying to reach Convertr. Researchers said they could see request traffic against /storybook in the logs, which is a strong smell. But they were careful about it, and so should we be. Sansec told BleepingComputer they could not confirm that CVE was definitively how the attacker got in.

That distinction matters. "Likely vector" and "confirmed entry point" are not interchangeable in an incident write-up, and sloppy reporting tends to blur them into certainty. The honest read: outdated software, a freshly disclosed exposed endpoint, suspicious matching traffic, and a skimmer already planted. Strong signal. Not a closed case on the forensic cause.

Blast Radius and the Cache That Won't Let Go

The exposure window started 24 October. Convertr confirmed to BleepingComputer that it has since cleaned the infection and upgraded Plausible to v3.0.1, the patched build. The company says it is now notifying affected merchants, payment providers, and the relevant authorities. Sansec independently verified that the tracker now served by analytics.convertr.app.br is clean.

But "the server is clean" and "your card is safe" are two different statements, and this is where the caching detail earns its keep. Sansec points out that the injected JavaScript could sit cached in a shopper's browser for up to 24 hours. If a browser had cached both the malicious script and a valid card number during that window, the skimmer could resurface and re-serialize that data even after the server-side fix. That's why the guidance isn't just "patch and move on." Affected consumers are told to replace compromised cards and clear their browser cache so the poisoned script can't reload from local storage.

The same campaign didn't stop at Convertr. The researchers found the group's skimmer active on two other sites during the same week: the travel platform 24hoursite and the UK fashion retailer La Fleur. Same pattern, same window, different brands. Convertr was the biggest catch, not the only one.

What a Security & Compliance Analyst Takes From This

Strip away the specifics and you're left with a lesson about the supply chain you didn't buy — one whose hidden time bombs are multiplying faster than teams can triage them. A checkout page is only as trustworthy as the slowest, most neglected dependency it loads. Convertr's merchants did nothing wrong. Their storefronts were silently compromised by a third-party tool none of them chose and most couldn't audit, and the platform that held the keys let a known-class exposure sit on a public endpoint.

Three habits fall out of this, and they aren't exotic. First, treat any self-hosted analytics or marketing tag in the checkout path as a first-class asset with a patch SLA, not as set-and-forget infrastructure. Second, version drift is a vulnerability class of its own; the CVE wasn't in the current release, yet a stale deployment made it exploitable anyway — a textbook illustration of why lagging vulnerability metrics and slow patch windows are themselves a risk. Third, cache TTLs are part of your remediation plan, not an afterthought, because a fixed server doesn't reach the stale copy already sitting on someone's laptop.

The group behind this has been running skimmers for years, and it keeps proving that the cheapest reliable path to card data is still the third-party script nobody thinks to look at — and the checkout pages that leak to human-led Magecart are the same ones now being drained by autonomous AI agent campaigns targeting hundreds of retailers. Your detection budget should follow the trust, not the perimeter.

Source: BleepingComputer — Hackers hijack Convertr analytics script to steal payment card data

one bad file, hundreds of stores, one checkoutone bad file, hundreds of stores, one checkout