October's Incidents Expose Different Paths Through Trusted Systems

PHP released fixes on Oct 21 for unauthenticated remote-code-execution flaws CVE-2026-109618 and CVE-2026-109619 in versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35.¹ The Canadian Cyber Centre's Oct 27 update reports exploitation in the wild and reports both vulnerabilities' Oct 26 addition to CISA's KEV catalog.² This is exploitation of vulnerable PHP installations, not evidence that the PHP project itself suffered a breach.^1,2

Previously in SitRep Oct 30: PHP2SHELL Attacks Achieve Root on Palo Alto Firewalls · CVE-2026-109618, CVE-2026-109619

Added to CISA KEV on 26 Oct 2026 (CVE-2026-109618, CVE-2026-109619) · CVE-2026-109618: CVSS 9.2, EPSS 1.00 (FIRST); CVE-2026-109619: CVSS 9.2, EPSS 1.00 (FIRST)

1. 1PHP · PHP critical security release and advisories
2. 2CANADIAN CENTRE FOR CYBER SECURITY · Critical vulnerabilities impacting PHP: exploitation update

Copy link to “PHP Flaws Face Active Exploitation”

LiteLLM's Oct 23 canonical report traces its malicious Oct 21 release, version 1.107.0, to an unrevoked admin key exposed in May and used on Oct 10 to steal GitHub tokens.¹ The report supersedes early theories and describes bypassed release protections and a malicious fork supplying PyPI and container artifacts.¹ Separately, StepSecurity identified credential-stealing @subql/common 5.8.3 on Oct 5; Aikido reported malicious tensorlake 0.5.144 on Oct 8 following repository activity on Oct 7.^2,3 These are distinct poisoned releases, not established breaches of npm or PyPI infrastructure.^1,2,3

1. 1LITELLM · The attack chain behind the v1.107.0 LiteLLM release
2. 2STEPSECURITY · SubQuery ecosystem compromise: hidden credential theft and backdoors
3. 3AIKIDO · Tensorlake npm package compromised

Copy link to “Poisoned Releases Target Developer Credentials”

GitGuardian's Oct 7 GhostAction report, updated Oct 9 and 13, describes compromised accounts used to plant credential-stealing GitHub Actions workflows; its Oct 8–12 wave targeted more than 30,000 repositories.¹ Wiz's Oct 25 Gheist report describes stolen-token abuse involving more than 850 compromised accounts, with activity since Sept 15 and secrets sought through Actions logs.² Targeted repositories are not all confirmed compromises, and neither report establishes a breach of GitHub's own infrastructure.^1,2

1. 1GITGUARDIAN · GhostAction returns: GitHub Actions supply-chain campaign
2. 2WIZ · Gheist: attempted scaled abuse of stolen GitHub tokens

Copy link to “Stolen GitHub Access Enables Secret-Stealing Workflows”

Cursor's Oct 29 notice, updated Oct 30, identifies malicious Anthropic.claude-code 2.1.312 and 2.1.313 distributed through its marketplace about 02:27–13:35 PT; Anthropic did not develop those malicious versions.¹ The payload collected host metadata, added an attacker SSH key and persistence, and attempted to enable SSH and open a reverse tunnel, with privileges and code errors usually blocking remote login.¹ Cursor removed the packages, rotated keys and said its audit found no other extensions tampered with.¹

1. 1CURSOR · Malicious Claude Code-branded extensions in Cursor marketplace

Copy link to “Cursor Removes Malicious Claude Code-Branded Extensions”

Railway confirms internal access and decrypted environment variables for some workspaces during Oct 20–22.¹ It estimates at most 1.85% of workspaces potentially affected; the exact variables remain unresolved.¹ Existing deployments stayed online while new builds paused; its Oct 26 update reports service restored for existing users.¹

1. 1RAILWAY · Preliminary Report: Oct 21st Security Incident

Copy link to “Railway Confirms Access to Stored Secrets”

Fireworks' Oct 9 PDT bulletin describes Oct 6 detection of unauthorized use of internal credentials accessing evaluation-job variables in limited customer accounts, with API keys and tokens believed captured.¹ It found no evidence of access to models, datasets, training data, personal information or inference traffic within its perimeter.¹ Separately, OpenCode said on Oct 17 that a breach exposed linked-provider API keys for 1.4% of Console users; some users reported unauthorized charges.² OpenCode's distillation-attack description is an attributed claim, not proof that model-provider systems were breached.²

1. 1FIREWORKS AI · Fireworks October 2026 security incident
2. 2BLEEPINGCOMPUTER · OpenCode Breach Exposes API Keys During AI Distillation Attacks

Copy link to “Fireworks and OpenCode Disclose Separate Credential Incidents”

PingCAP's Oct 19 report says stolen service-account credentials enabled internal-system access and copying of records and source code from Sept 9 to Oct 7.¹ Affected records included TiDB Cloud account details, SQL editor text and errors, business and billing data, and encrypted API-key values.¹ Customer-specific scope and usable-credential exposure remained unresolved; investigators found no evidence that data stored in TiDB was affected.¹ By Oct 14, identified compromised credentials had been invalidated and identified access paths blocked.¹

1. 1PINGCAP · October 2026 incident report: unauthorized access to PingCAP cloud resources

Copy link to “PingCAP Reports Internal Record and Source-Code Exposure”

Polymarket's Oct 30 postmortem says a compromised third-party performance-monitoring script used active sessions on Oct 29 to sell positions and move wallet funds.¹ The company removed the script, paused trading and reset active sessions before reopening.¹ Its $3.9M refund total combines $2.7M attack losses and $1.2M compensation for the trading pause.¹ The official postmortem does not identify the vendor by name.¹

1. 1POLYMARKET · October 29 vendor-script incident: October 30 postmortem

Copy link to “A Vendor Script Drains Polymarket Wallets”

SoftBank's Oct 19 notice describes attempted unauthorized access on Oct 17 and precautionary suspension of My SoftBank, My Y!mobile and My Menu websites, without establishing customer-data theft.¹ Separately, subsidiary IDC Frontier's Oct 27 final report says Oct 7 ransomware exploited authentication software and disrupted cloud services for 495 organizations.² Registration data for up to 71 organizations was improperly queried, while investigators found no evidence of virtual-machine data exfiltration.²

1. 1SOFTBANK · Notice concerning attempted unauthorized access to customer websites
2. 2IDC FRONTIER · Final investigation report on the IDCF Cloud security incident

Copy link to “SoftBank and IDCF Report Distinct Incidents”

Capcom's Oct 22 notice says unauthorized access detected Oct 19 affected 11,774,247 email/login-metadata records, with additional profile data in 43 records.¹ Attackers changed passwords on 196 accounts; Capcom reset them and had not confirmed compromise of customers' original passwords.¹ Its Oct 23 update confirms access to personal, purchase and inquiry details in 19 e-Capcom store accounts; payment-card data was not affected.² Capcom warned customers to watch for phishing; its notice did not report a resulting phishing campaign.¹

1. 1CAPCOM · Notice of customer information affected by unauthorized access
2. 2CAPCOM · Update on unauthorized changes to CAPCOM ID passwords

Copy link to “Capcom Separates Record Exposure from Account Takeovers”

Coinbase told Unchained on Oct 28 that an Amplitude incident affected contact and limited transaction data; it found no evidence of Coinbase-system access and said funds were unaffected.¹ Amplitude's Oct 28 notice dates detection and containment to Sept 28; its under-0.3% figure concerns its customer accounts, not Coinbase users.² Warp's CEO said on Oct 26 that unnamed-vendor exploitation identified Oct 23 may have exposed limited agent traces and telemetry, with roughly 1% of users potentially affected.³ Warp's vendor identity and code, prompt or credential exposure were not established, and the agent-swarm explanation remains unverified.³

1. 1UNCHAINED · Coinbase spokesperson explains Amplitude data impact
2. 2AMPLITUDE · Customer update: recent security incident
3. 3BLEEPINGCOMPUTER · Warp Breach Exposes AI Agent Logs and Telemetry Data

Copy link to “Coinbase and Warp Report Distinct Vendor Incidents”