The WISPer Report

Part of my job as researcher is to keep track of what's current in cybersecurity. The other part of my job is to translate that technobabble into plain English for the layperson, because public awareness and education in the digital age has been deliberately gutted.

Posts made here are simultaneously uploaded on LinkedIn and Reddit as well, and our company has plans to expand our online presence further.

Of Note:

I currently have the askbox anon on. Play nice, or lose the privilege. Same goes for reblogs and replies. This is a professional space, please act accordingly. This is not customer service and I can and will block with impunity.

Don't expect me to take anything at face value. I'm a researcher, my job is fact checking.

I will check this blog daily as I update it. Any questions in my inbox will be answered at that time.

About Me:

I've worked for WISP since 2021, starting as a student, then intern, and learning up the ladder to my current position as forensic analyst.

I come to cybersecurity via the life sciences. I have a degree in Biotech that's been remarkably handy in my current job. I am older than the internet. I remember when computers were still in monochrome and had no mouse. I have watched my industry be born.

I am anti-censorship and anti-generative AI. I have a private life that I endeavor to keep private. But I feel comfortable enough to share that I am the parent of one child and two cats. I play video games. I enjoy my work that is essentially 'sort, sort, arbitrarily sort'. Of course I have blue hair and pronouns (she/her), I work in Infosec.

Several cybersecurity news outlets are covering the announcement from Apple regarding a new notification warning for iPhone users in over a hundred countries today. And it’s one that users should be taking seriously. We are living in a growing state of surveillance, where one’s every location, message, purchase, and behavior is tracked, often without their consent or in violation of their rights to privacy. The new alert will now tell users when their phone detects mercenary spyware targeted at them.

So what is mercenary spyware? As defined by EM360 Tech, it’s a type of malicious software developed and sold by private companies to governments, law enforcement agencies, and sometimes private individuals, and is designed for targeted surveillance. If an infostealer and a spearphishing campaign had a lovechild, it would mercenary spyware. Targets of this attack are generally journalists, human rights defenders, lawyers, political figures, diplomats, and civil society organizers, according to both Cyber Security News and The Hacker News. These victims are usually high value from an intelligence standpoint. But they are not the only ones, and Apple urges their users to take the alert seriously, rather than treating it like a joke, routine phishing warning, or generic security tip. The alert creates a popup on the lockscreen, can be seen in the Settings under ‘Apple Threat Notification’, or at the top of one’s account page when logged in. The wording of the warning is simple: ‘Apple detected a mercenary spyware attack targeted at your iPhone. There are actions you can take now to help protect your data and device.’

Among those actions is putting the device in Lockdown Mode, which is an optional but extreme security feature designed to reduce an iPhone’s attack surface by aggressively limiting message attachments, complex web technologies, unknown FaceTime calls, configuration profiles, and wired connections. Frankly, these limitations are all good practice anyway, and Apple states that they have not yet observed a successful compromise of a device with Lockdown Mode enabled. It will degrade some functionality of the device, but to my mind is no different than other strict browsing or messaging settings. Why would one leave their device unsecured in this day and age to begin with? (I keep my own phone at the strictest settings, but I’m an Android user.)

Apple also suggests subscribing to Access Now’s 24/7 Digital Security Helpline, which is a free support service for at risk users. And of course, keep the device up to date, a somewhat more difficult prospect given how often the software updates and the economically baffling expectation that every user has the ability to replace their device repeatedly to keep up with increased processing demands. Much simpler, but equally as recommended, is keeping the device secure using a passcode, Touch ID, or Face ID, enable two-factor authentication for one’s account, turn on Stolen Device Protection, install apps only from trusted sources, and do not open links or attachments from unknown senders. The usual precautions.

iPhone users are not the only potential victims of mercenary spyware, as it has also been seen in Android and iOS devices. But to my knowledge, Apple is the first to take an active stance on warning their users of its detection. I know there is a tendency towards complacency regarding popup warnings, but that does not mean they should be ignored. Users are at risk; paying attention is also good practice.

In March, I covered several reports of the Trivy breach, carried out by TeamPCP. The attack exploited the vulnerability scanner, harvesting SSH keys, cloud credentials, Kubernetes tokens and cryptocurrency wallets to then move laterally through supply chains in GitHub and PyPI. At the time, the threat actor coordinated with a ransom-as-a-service operator, Vect, to further encrypt the stolen data. Half a year later, we’re still seeing the results.

The Hacker News published an article yesterday cataloging the downstream effects of the Trivy breach, determining that over 2K organizations may still be compromised. A compilation from roughly 434,000 files are not individual victims but, according to CloudSEK’s research, a total of the data stolen during the campaign. CloudSEK has published their findings in a dataset as a public lookup, searchable by name or domain and filterable by confidence. Mostly what that means is that if one looks up their organization, they can find whether or not they are likely to be carrying the poisoned packages inserted into the supply chain during the attack.

Many of the companies in the dataset may not actually be compromised (ie – the stolen credentials were never used), but CloudSEK and LiteLLM are saying that these should be rotated anyway, just in case. LiteLLM is an open-source AI gateway used to connect applications with multiple model providers, and was part of the initial Trivy breach’s victims. Two version of a PyPI package were identified as compromised – 1.82.7 and 1.82.8 – and were removed from circulation. They were available for less than an hour on a single day back in March. However, the platform recommends treating anything downloaded that day as suspect. Previous, clean versions are still available.

The reason for such an abundance of caution lies in the credentials themselves. CI/CD secrets, publishing tokens, and cloud credentials accessible during the relevant exposure windows could still be at risk if they haven’t been rotated or revoked. I mean, that’s rather obvious, isn’t it? Not changing the locks on the doors after someone steals your keys is tempting fate for your house to be broken into. And yet it occurs a surprising amount of the time after a compromise. People rely on luck to not get dinged, or simply don’t communicate with their own security teams enough to know or understand what’s at stake. Or simply don’t want to expend the effort. Compliance apathy is every bit as dangerous as knowingly risky behavior.

There are some conflicting reports on the fallout of the Trivy attack, but ultimately they come down to how the campaign was deployed versus how the stolen data was used. Which are just different stages of the same attack chain, CloudSEK asserts. Either way, the fallout is clear. Months after the breach, organizations remain at risk of compromise. Even assuming that the scale of CloudSEK’s dataset may be inaccurate or exaggerated, the downstream impact is confirmed. Checkmarx said credentials obtained through the Trivy attack enabled unauthorized access to its GitHub repositories and the publication of malicious artifacts. Mercor said it was affected by malicious LiteLLM versions and contained unauthorized activity. There’s no denying the attack happened and has had far reaching consequences. But it’s not hard to prevent further data loss with simple credential rotation and token renewal.

Another month, another restart of my computer. This month’s Patch Tuesday includes fixes for 400 flaws, addressing one actively exploited and two publicly disclosed zero-day vulnerabilities, as well as 42 critical vulnerabilities, 37 of which are remote code execution and 5 are elevation of privilege.

Bleeping Computer covers only those fixes released by Microsoft on this day. They are: 176 Elevation of Privilege Vulnerabilities, 11 Security Feature Bypass Vulnerabilities, 110 Remote Code Execution Vulnerabilities, 86 Information Disclosure Vulnerabilities, 12 Denial of Service Vulnerabilities, and 21 Spoofing Vulnerabilities. As always, more details are available for these patches in the linked article, or the full report can be viewed here. Flaws in Mariner, Microsoft Teams, Microsoft Azure, Microsoft Entra, Microsoft Office, and Power Apps were fixed by Microsoft earlier this month. While not as large as July’s record breaking Patch Tuesday of 570 flaws, this month’s is still large. Microsoft predicted this would be the case, since they’ve starting using an AI-powered vulnerability discovery system to identify more security flaws across its software products (for better or worse).

There were also patches carried out by other companies, as is typical. Adobe released security updates for vulnerabilities in Coldfusion, Commerce, Lightroom Classic, Content Credentials SDK, and Campaign Classic. Cisco released security updates for numerous products, including Cisco Catalyst SD-WAN, IOS, IOS XE, and ClamAV flaws with public exploits. Metabase released security updates for a critical SQLi flaw that was exploited in data-theft attacks. N-able released security updates for an actively exploited authentication bypass vulnerability (CVE-2026-18577) affecting both hosted and on-premises N-central servers. SAP released the August security updates for numerous products, including a 10.0-severity improper authorization flaw in SAP Commerce Cloud (Data Hub Adapter). TP-Link patched 15 vulnerabilities in the zero-touch provisioning (ZTP) mechanism of its Omada network devices that could lead to RCE. And VMware released security updates for VMware Avi Load Balancer, which include authentication bypasses and remote code execution flaws. Each of these have more details by following the links in the article.