There is at least one Adobe Reader 0day being exploited in the wild:
https://justhaifei1.blogspot.com/2026/04/expmon-detected-sophisticated-zero-day-adobe-reader.html
TL;DR: One 0day is being used to simply communicate details to a C2 server to get further commands. Specifically, there is a vulnerability that allows reading arbitrary local files using Reader JavaScript. In this case, ntdll.dll and friends, so that the C2 knows specifically what version of Windows the victim is running.
Nobody knows what secondary payload the C2 is delivering to selected targets. But it's a direct pipeline to allow the C2 to run arbitrary JavaScript on the victim system.
So I'll bet dollars to donuts that there is a second more powerful vulnerability that the attackers have up their sleeves. Or at the very least, the same vulnerability that allows the privileged file read might be able to be leveraged to do something nasty. And the whole AES-encrypted C2 stuff is merely to not put the payload statically in the exploit PDF, allowing a dynamic payload for any given target.
cpuid has been compromised, most downloads are serving a rat+infostealer as we speak, make sure you didn't get hit
We publish a major Citizen Lab report on Webloc, an ad-based mass surveillance system that monitors the movements and personal characteristics of hundreds of millions people globally based on data obtained from mobile apps and digital advertising.
Customers include ICE, El Salvador and Hungary.
Our research shows that ad-based surveillance is now used by military, intelligence and law enforcement agencies down to local police in several countries.
Full report here:
https://citizenlab.ca/research/analysis-of-penlinks-ad-based-geolocation-surveillance-tech/
Very slightly work adjacent: a "we've updated our privacy policy" email in my inbox reminded me of a thing that $work did, and that I wish every company did: we checked all our ToS and similar documents into a git repo and published it, so that when they change you can just go look at the damn diff and see what changed (https://github.com/tailscale/terms-and-conditions).
If you work someplace and have the authority to do this, I wish this was normalized and expected of corporations that expect us to ingest a short story worth of legalese and keep up with the changes over time.
Near as I can tell, this is all very good news. More things should take advantage of secure enclaves, and this open standard protects against one of the hardest current defense surfaces.
https://security.googleblog.com/2026/04/protecting-cookies-with-device-bound.html
Former Trenchant exec who stole exploits from his employer and sold them to a Russian broker says he was suffering depression & money troubles when he decided to sell the exploits. Also, new info reveals the nature of the work he did for an Australian intel agency before joining Trenchant. My story is linked below. Please consider becoming a paid subscriber if you like my work on this piece. It's 4,000 words and I'm making it available for free to everyone. But I can only do that because some subscribers have generously become paid subscribers.
I came across a reference to #Wazuh in another thread. It looks interesting: an open-source thing that can manage a bunch of compliance requirements.
So I went looking for information about their agent's security. Things I did find:
Things I did not find:
Are these things somewhere I missed? Anyone familiar with the project know how they avoid their network-connected-and-highly-privileged thing being an attack vector for client devices? Is it possible to run it sandboxed with read-only access to the system (for reporting violations but not automatically trying to fix them)?