A new Russian loader-as-a-service named DOUBLECUP uses ClickFix attacks to hide malicious code in PNG images cached by victims' browsers, ultimately delivering CountLoader to Windows and macOS devices and a new remote access trojan named DeviceManager to Windows systems.
For defenders, the useful question is what this changes about exposure, timing, trust, or control assumptions before the issue turns into someone else's incident review.
What To Know
The real value here is separating the headline from the operational facts: who may be exposed, what preconditions matter, and what readers should verify for themselves.
Reading an older article? Use the brief to stay current.
This Article Gives You the Background. The Brief Gives You What Changed Next.
Get the weekday cyber brief for new policy moves, CISA actions, and risk developments this article could not cover when it was published.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
Why CyberExperts Flagged It
The useful question is not whether this is interesting. It is whether it changes what defenders should prioritize, explain, or stop underestimating.
This matters because ClickFix-style attacks keep evolving faster than user awareness programs do. Hiding payload stages in browser cache artifacts gives attackers another low-friction way to turn a convincing prompt into malware execution.
What Defenders May Be Underestimating
The hidden risk is often not raw technical complexity. It is uncertainty around exposure, ownership, timing, or how much operational drag a delayed response can create once attention shifts from the vulnerability itself to its consequences.
Reading an older article? Use the brief to stay current.
This Article Gives You the Background. The Brief Gives You What Changed Next.
Get the weekday cyber brief for the developments, risk shifts, and new signals that changed the picture after this article was published.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
What Teams Should Do Next
- Check asset ownership, remediation timing, and whether this belongs in the current cycle instead of the someday pile.
- Check whether the tactics described map to your current detection coverage, logging visibility, and user or developer exposure points.
- Brief the relevant owners early if the story suggests a shift in attacker tradecraft rather than just another isolated sample.
- Track the original source for updates, scope changes, or newly published mitigation details.
Source Context
CyberExperts is using BleepingComputer as the primary reference for this update.
Related In The Daily Brief
See this item in The 5-Minute Cyber Brief
Newer CyberExperts coverage on this topic
This article still works as background. If you want the current picture, start with the freshest related coverage below and today's brief.
Coder’s registry infrastructure compromised to push malicious modules
The Coder incident is a supply-chain lesson in miniature: once attackers can tamper with trusted module distribution, defenders are no longer verifying...
Attackers Turn Trusted Node.js Runtime Into Malware Delivery Tool in Targeted Attacks
The useful lesson in this campaign is not that Node.js is bad. It is that adversaries keep choosing legitimate runtimes defenders already...
HPE patches critical ArubaOS-CX remote code execution flaw
ArubaOS-CX deserves attention because switching software rarely gets treated with the same urgency as identity or edge security until exploitation arrives. A...
The 5-Minute Cyber Brief: September 18, 2026
The fastest way to catch up on what changed after this article was published.
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.
