Your Latest Magento Patch Wasn't the Problem

A zero-day the researchers at Sansec are calling StyleSmuggler (CVE-2026-75650, rated CVSS 10.0) has been quietly installing backdoors in Magento Open Source and Adobe Commerce since September 4, and the detail that should make any store operator pause is not the one in the headline. The first recorded compromise landed on a target running the newest security updates. Every version from 2.4.4 up to and including 2.4.9 is affected, and no login is required to get in. The bug slips malicious PHP into Magento's template system through the styles properties, riding past the existing safeguards, and then gets triggered by something totally mundane: a fake "failed payment" email. Unauthenticated remote code execution on a platform installed on more than 160,000 sites, about 14,000 of them in the top million. Adobe dropped an emergency hotfix on September 7 under APSB26-146, but "patched" is doing a lot of heavy lifting in a sentence like that, and this is why.

Because the thing Sansec is dropping isn't a noisy webshell you can find by grepping for obvious junk. It's a small Rust-based backdoor that shows up as a background process wearing the name [kworker/u:8:0], and newer samples disguise themselves as fc-cache and copy themselves into ~/.cache/fontconfig/. That's the part that actually matters to the people in the room: the malware is impersonating the exact kind of kernel worker process and font-cache artifact you've been trained to stop looking at. Add a cron job that re-runs the payload every 30 minutes for persistence, and the failure mode for a "compromised" server stops being a question you answer by checking versions and starts being a question you answer by going hunting for persistence. If you're running a Magento store right now, the useful mental shift is that the September 4 incident means the patch is the floor, not the verdict. You have to assume the door was opened while you were still on the latest build, and work backward from there for what got installed and when.

Source article image
Source image 1

That's the lesson that transfers beyond Magento specifically: when a zero-day's first in-the-wild hit is on a fully current install, "we're patched" stops being a defensible answer to "are you compromised?" It's a necessary condition, not a co

The Hacker News Logo
Source image 2
nclusion. So I'd like to hear from the folks who actually run these stores — when the patch clearly didn't save you, what's your real process for hunting the persistence? Do you rebuild from known-good images, or do you try to carve the backdoor out of a running box and trust what you're left with?

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

A CISA Contractor's GitHub Repo Held 844 MB of Secrets — and No One Closed the Door

Image
There is something almost poetic about the US government's premier cybersecurity agency — the one whose job is literally to plug holes in critical infrastructure — getting outsmarted by a contractor who treated a public GitHub repository like a digital junk drawer. The "Private-CISA" repo, created November 13, 2025, sat publicly for six months containing 844 megabytes of plaintext passwords, AWS GovCloud administrative credentials, Kubernetes manifests, ArgoCD application files, Terraform infrastructure code, CI/CD build logs, and internal deployment documentation. Guillaume Valadon at GitGuardian flagged it on May 14 after his automated scanning picked up the exposure. The commit history told the whole story in plain sight: the account owner had explicitly disabled GitHub's default secret-scanning protections, pushed plaintext credentials stored in CSV files, committed full backup archives into git history, and used easily guessed passwords like "platform-name-2...
Read more