Cyber Chronicle

TRENDS, THREATS & TACTICS FOR CYBER CERTAINTY™

BY DANIEL TOBOK

November 2026

What This Is:
  • A monthly intelligence briefing on the most significant cyber trends, threats, and tactics — curated specifically for business leaders and security professionals.
  • Real-world incidents and developments, analyzed through the lens of Cyber Certainty™.
  • Focused on one outcome: turning awareness into decisive action.

Why It’s Important:

  • The organizations that get hit hardest are not always the ones with the weakest technology. They are the ones that were not prepared when the moment arrived.
  • Business and security leaders are being asked to make high-stakes decisions faster than ever — and the cost of getting it wrong has never been higher.
  • This briefing exists to close the gap between what is happening in the threat landscape and what your organization is doing about it.

Purpose:

  • Deliver clarity on the developments that matter most this month.
  • Help leaders respond with speed and confidence — not fear and confusion.
  • Reinforce the Cyber Certainty™ principle: preparation is not optional. It is your most strategic advantage.

NEW ALL-TIME RECORD LEVELS OF CYBER THREAT AND CONCERN: Global Trends & Threat Levels At An All Time High

CYBER TRENDS:

PHP2SHELL PUT APPROXIMATELY 36.7 MILLION INTERNET-FACING SERVICES AT POTENTIAL RISK — The Coordinated Disclosure Fell Apart Before the Patches Shipped

Article: PHP2Shell Exploitation: Two Critical PHP Flaws Explained

On October 21, 2026, the PHP security team released emergency patches for two critical remote code execution vulnerabilities — CVE-2026-109618 and CVE-2026-109619 — collectively named PHP2Shell. Both are rated CVSS v4.0 9.2. CVE-2026-109618 exploits memory corruption during out-of-memory error handling; CVE-2026-109619 targets stale global state where a PHP worker accesses references to memory freed after a previous request. Either can be triggered by an unauthenticated attacker. A Censys snapshot taken on October 22, 2026, one day after the patches shipped, identified approximately 36.7 million internet-facing services running potentially vulnerable PHP versions. What made this incident especially damaging was the disclosure sequence: CVE identifiers leaked online on October 20 — before coordinated disclosure — forcing defenders into a compressed response window against attackers who already had a 24-hour head start.

My thoughts:

What PHP2Shell exposed is not primarily a flaw in PHP — it is a flaw in the coordination model that modern vulnerability disclosure depends on. The CVE identifiers for these two flaws were public before a single patch existed. Security researchers confirmed they had reproduced CVE-2026-109618 in lab environments and withheld technical details while patches were still being prepared. Dark web forums were active. Bitsight assigned exploit likelihood scores of 9.91 and 9.84 out of 10. One post on an exploit forum stated plainly that the internet would be on fire. That warning underscored the urgency of the situation, although reports of the scale of exploitation initially varied.

The scale of exposure here is not a coincidence of timing. PHP powers roughly 77 percent of websites that use a known server-side language — WordPress, Drupal, Joomla, and thousands of custom applications all run on the same runtime that contained these flaws. When a vulnerability in that runtime allows unauthenticated remote code execution, the potential attack surface is not one application or one industry. It is the foundational layer of the internet. Government websites in multiple countries took themselves offline rather than wait for the patch. The NSA advised organizations to update immediately or go dark. That is not a routine patch advisory.

The lesson I draw from PHP2Shell is about the gap between the moment a CVE leaks and the moment your environment is patched. In this case, that gap was measured in hours — and attackers were already searching for targets before the gap existed. If your patch deployment depends on a scheduled maintenance window, a change management approval process, or manual validation of each affected system, PHP2Shell is the clearest current proof that the adversary’s clock does not wait for yours.

What can we do?

Confirm your PHP version immediately. The fixed releases are PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35 — all released October 21, 2026. If your hosting provider or managed service manages PHP on your behalf, confirm with them directly that the update has been applied, and ask for a version confirmation rather than a general assurance. Patches cannot be assumed; they must be verified.

As an interim mitigation, set session.upload_progress.enabled=0 in your php.ini configuration. PHP’s own advisory identified this setting as reducing the exposure surface for CVE-2026-109619. It does not eliminate the vulnerability, but it narrows confirmed attack paths while patching is underway. This setting also covers a third flaw, CVE-2026-115560, disclosed shortly after the initial patch release.

Business leaders should treat PHP2Shell as a test case for your emergency patching posture. Ask your security or IT team: what is the actual time between a critical vulnerability disclosure and confirmed patching in our environment? If the answer is measured in days or weeks rather than hours, that gap is not theoretical — it is your current risk exposure in every future incident like this one.

CYBER TACTICS:

YOUR AI GATEWAY JUST BECAME THE MOST DANGEROUS SINGLE POINT OF FAILURE IN YOUR TECH STACK — The LiteLLM Supply Chain Compromise Shows Why

Article: LiteLLM Compromised in Supply Chain Attack — Credential Stealer and RAT Delivered via PyPI

On October 21, 2026, attackers published a malicious version of LiteLLM — version 1.107.0 — to the Python Package Index, Docker Hub, and GitHub Container Registry. LiteLLM is an open-source AI gateway used to route requests to multiple large language model providers, with approximately 23 million weekly downloads. The malicious build contained two payloads: a credential stealer named privcollect, which runs every time Python starts and collects cloud tokens, API keys, browser credentials, and environment variables, exfiltrating them encrypted to a lookalike domain; and a second-stage remote access trojan that can receive commands on an ongoing basis. Attackers gained access to the release pipeline by compromising GitHub CLI OAuth tokens from three engineers’ accounts, then pointing a release workflow at a lookalike repository. The malicious PyPI package was available for approximately 104 minutes, while compromised Docker Hub images remained available for approximately 153 minutes before containment. This is LiteLLM’s second supply chain compromise in 2026 — the first, in March, produced a 153 GB stolen archive linked to 2,488 corporate domains.

My thoughts:

What this incident documents is the specific security problem created by AI infrastructure at scale. LiteLLM is not a productivity tool. It is a broker. Every API key for every LLM provider your organization uses — OpenAI, Anthropic, Google, Azure, Amazon Bedrock — passes through it. The credential stealer in version 1.107.0 was built with that architecture in mind. It specifically targeted AI tooling credential JSON files alongside cloud tokens and developer accounts. The malware was designed to target sensitive credentials across AI tooling, cloud environments, and developer systems, highlighting the broader risks of compromised AI infrastructure. 

LiteLLM’s updated post-incident investigation revealed that the breach originated from a master key accidentally exposed in a public repository in May 2026. Although the exposure was identified, the key was not revoked. Attackers later used it to access an internal agent platform and obtain a GitHub organization owner’s OAuth token. They subsequently compromised additional maintainer credentials through malicious CI workflows and manipulated the release pipeline to distribute infected packages. The incident highlights how unrevoked credentials, excessive privileges, and compromised development workflows can turn a single security lapse into a widespread supply chain attack. 

The 104-minute window between publication and takedown sounds like a fast response. It is. The containment was effective and the LiteLLM team acted quickly. But 104 minutes is long enough for an automated installer running in a CI/CD pipeline to pull the package, execute the install, and have privcollect running in a production environment before anyone notices. The question is not whether your team would have caught it within two hours. The question is whether your pipeline would have installed it before your team had a chance to.

What can we do?

If your organization uses LiteLLM, confirm that no environment installed PyPI version 1.107.0 or pulled the affected Docker image tags (v1.107.0, latest, main-latest, or main-stable) during the October 21 exposure window. Use a verified clean version and conduct a credential audit for any environment that may have run an affected package or container image, even briefly. Rotate all API keys and cloud tokens that were accessible from those environments. Deleting the package is not sufficient — privcollect installs a .pth file that persists after removal. The stealer sentinel file left by the malware is /tmp/.pc_once_72129118c59f5636c0bb; confirm it does not exist on any affected system.

Audit your AI gateway logs for credential exposure. Determine whether your LiteLLM deployment is logging response bodies. If it is, review those logs for any tokens or credentials that may have been embedded in responses. This is not a LiteLLM-specific issue — any gateway that logs full response content can accumulate credentials over time without anyone realizing it. Establish a log retention and scrubbing policy that specifically accounts for AI gateway traffic.

Business and technology leaders should add AI infrastructure to their software supply chain security posture. The same package verification, dependency pinning, and SBOM practices that apply to production application code should apply to AI tooling. An AI gateway with 23 million weekly downloads is not a peripheral utility — it is core infrastructure, and it should be treated with the same scrutiny. If your team does not currently have a process for evaluating supply chain risk in AI tooling specifically, this incident is the reason to build one now.

CYBER THREATS:

A STOLEN VENDOR CREDENTIAL ENABLED SUCCESSFUL SIGN-INS ACROSS MORE THAN 300 TENANTS — The ConnectWise Cloud Backup Breach Is the Clearest Warning Yet About Third-Party Trust

Article: Hackers Breach Microsoft 365 Tenants via ConnectWise Supply-Chain Attack

On October 15, 2026, attackers used a stolen application credential belonging to ConnectWise Cloud Backup — formerly SkyKick Cloud Backup — to authenticate as the backup service inside customer Microsoft 365 environments. Because that single credential was trusted by every organization that had granted the application access, one compromised secret became a key that worked in hundreds of separate tenants simultaneously. Microsoft Threat Intelligence characterized the incident as an active supply chain attack. Huntress identified suspicious sign-in activity across almost 1,000 Microsoft Entra tenants, with more than 300 successful sign-ins. However, a successful sign-in did not necessarily indicate confirmed data access or compromise. ConnectWise suspended its Cloud Backup, SaaS Security, and Cloud Management services on October 17. Separately, Microsoft confirmed that a China state-aligned threat group designated Storm-0940 used AI agents — a framework called ARTEX — to accelerate the campaign, moving from initial target selection to privileged cloud access in under three hours in several documented attacks.

My thoughts:

What ConnectWise has documented here is one of the most instructive supply chain incidents in recent years — not because the technical method was sophisticated, but because of what it reveals about the trust architecture most organizations have built around their cloud environments without examining it.

Cloud backup services occupy a position of extraordinary privilege in any Microsoft 365 environment. To do their job, they need read access to every mailbox, every file in SharePoint and OneDrive, every Teams conversation, and often the entire directory. Organizations grant that access deliberately and correctly — it is necessary for the service to function. What the ConnectWise incident demonstrates is that this access does not expire, does not require re-authentication from a known IP address, and is only as secure as the application credential held by the vendor. A single stolen secret at ConnectWise became the master key to the email, files, and directory data of hundreds of organizations their customers served.

The AI acceleration component documented by Microsoft should not be treated as a footnote. Storm-0940’s ARTEX framework handled reconnaissance, privilege escalation, and persistence tasks autonomously, with limited human direction, at machine speed. The campaign targeted hundreds of organizations. When the attacker’s tooling operates faster than any human analyst can triage alerts, the response requirement is no longer operational speed — it is architectural design. You need controls that detect and terminate malicious authentication before a human analyst reads the alert, not after.

The hardest part of this incident is not remediation — it is the realization it forces about third-party access as a category. ConnectWise did not fail because they were negligent. They were targeted because their application credential was an extraordinarily high-value asset. Any vendor with that level of standing access to your environment is, by definition, a critical node in your security architecture. Most organizations have dozens of such vendors and have never reviewed the permissions they hold collectively.

What can we do?

If your organization uses ConnectWise Cloud Backup or relies on an MSP that uses it, conduct an immediate audit of your Microsoft 365 tenant for signs of unauthorized activity between October 15 and October 17. Specifically: review the Entra ID audit logs for service principal authentication from unexpected IP addresses, check whether any new credentials were added to application registrations, and confirm whether any Global Administrator or Directory role assignments were made during that window. ConnectWise stopped the attack, but your organization is responsible for determining whether persistence was established in your tenant before they did.

Review every third-party application in your Microsoft 365 environment that holds elevated permissions — particularly Directory.ReadWrite.All, Mail.ReadWrite, or any role that grants access to user data across the entire tenant. For each one, ask three questions: Is this access still necessary? Is the vendor’s credential protected with the same rigor we apply to our own privileged accounts? What would an attacker be able to do if that vendor’s credential were compromised tomorrow? If you cannot answer those questions, you have not fully evaluated your supply chain exposure.

Business leaders should understand that the Conditional Access policies you have applied to your own users do not automatically extend to service principal authentication. A policy that requires MFA and blocks sign-ins from unknown locations will not stop an attacker who is authenticating as a trusted application credential — because application credentials do not go through the same authentication flow as users. Ask your security team whether Conditional Access for workload identities is in place, and whether service principal sign-ins from unexpected IP addresses would generate an alert your team would see in time to act.

If Cyber CertaintyTM matters to you, your company or business, then subscribe to Daniel’s thought leadership today

    Social Media

    ©2026 Daniel Tobok. All rights reserved.