Veracode Daily Threat Intel Brief | 2026-11-02

Join the VERACODE Community Group - Product & Security Tips - for the latest Veracode Daily Threat Intel Brief - Stay current, stay secure!

https://community.veracode.com/s/group/0F9Uf0000001c01KAA/product-security-tips

 

CISO Advisory Brief | Monday, November 2, 2026 | Coverage: last 24 hours, 7 and 30 days

 

 

1. Executive Snapshot

Five actions for the next 24 to 72 hours, in priority order.

  1. Patch PHP2Shell and the Linux kernel flaw that chains with it. CISA lists CVE-2026-109618 and CVE-2026-109619 as exploited (added October 26, federal due date October 29) and says Linux kernel CVE-2026-46300 can be chained with them to plant PHP webshells and run commands as root (added October 28, due October 31). Move PHP to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, patch kernels, and include PHP embedded in vendor products and appliances.
  2. Patch Ivanti Connect Secure, then hunt for compromise. CISA added CVE-2026-111357 (federal due date today, November 2) and CVE-2026-118527 (due November 13) on October 30. Both were used as zero-days alongside CVE-2026-104935. A clean result from Ivanti's Integrity Checker does not rule out compromise (single source: Volexity via Help Net Security), so preserve logs and memory before resetting.
  3. Upgrade self-managed GitLab. CVE-2026-97229 allows unauthenticated code execution through a crafted regular expression in CI/CD configuration; CISA added it on October 29 and the federal due date passed yesterday. Move to 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10 or 18.11.13, which also fix the unexploited CVSS 10 flaw CVE-2026-110264. Then rotate tokens, deploy keys and server secrets.
  4. Find every bundled copy of the Brotli decoder (CVE-2026-111497, Node2Shell). CISA added it October 27 with a November 10 federal due date. Upgrade Node.js to 26.12.1, 24.22.1 or 22.23.4 and Brotli libraries to 1.0.10, 1.1.1 or 1.2.1, then rebuild and redeploy container images.
  5. Sweep developer tooling for three confirmed supply-chain campaigns. Search every repository, private ones included, for ci-sync-* branches and a sync-check workflow (Gheist). Look for .github/init.js and unexpected Claude, Gemini, Cursor or VS Code settings files (testmetest). Check developer machines for the SSH key labeled svc-telemetry from the tampered Claude Code extension on Cursor's marketplace. On any machine hit by testmetest, remove persistence before revoking tokens.

 

2. High-Visibility Breaches

  • Binance — About $6.3B in crypto left Binance wallets on October 29, mostly within about 20 minutes; Binance says it will cover customer losses. Attacker/method: FBI attributes it to North Korea's TraderTraitor. Binance's preliminary finding is a compromised DevOps engineer's laptop; TRM Labs assesses the hot-wallet signing infrastructure was compromised. Confidence: Attribution confirmed (FBI). Root cause UNCONFIRMED. Sources conflict on the loss ($6.3B to $6.43B) and on chains hit (10 or 11).
  • ConnectWise customers — Storm-0940 used compromised ConnectWise Cloud Backup application identities to attempt sign-ins to more than 2,250 Microsoft 365 tenants; some saw persistence and privileged-role changes. Attacker/method: China-state aligned Storm-0940, using the ARTEX agentic AI framework. In some cases initial targeting to privileged cloud access took under 3 hours. Confidence: Confirmed (Microsoft original report, SecurityWeek, CyberScoop). Tenant count is attempts, not confirmed data loss.
  • Polymarket (via DebugBear) — About $2.7M drained on October 29; Polymarket is refunding $3.9M in total, including losses from the trading halt. Attacker/method: DebugBear's DNS was hijacked through its registrar and served a wallet-draining script that reused traders' live sessions. Confidence: Confirmed by both companies. Wallet count differs: 726 (Polymarket) vs 737 (Bitquery).
  • Cursor Marketplace — Tampered Claude Code extension versions 2.1.312 and 2.1.313 were live for about 11 hours on October 29; up to 5,000 users. Attacker/method: Adds an attacker SSH key and reverse tunnel with startup persistence. How the attacker published to Cursor's marketplace is not explained. Confidence: Confirmed (Cursor notice, Microsoft analysis). Anthropic says its own channels were unaffected (single source).
  • Keystone — Device-authentication key and 25,964 buyer records exposed; 18,835 devices in stock will be destroyed. Attacker/method: A flaw in a third-party data monitoring tool on its website was used to escalate privileges; found October 20. Confidence: Confirmed by company (two sources).
  • Chainalysis — Customer user IDs, names, email addresses and role labels accessed. Attacker/method: Company says the attacker used offensive agentic techniques; entry point and actor not disclosed. Confidence: Confirmed by company (two sources); scope still under investigation.

 

The full brief continues in the answers below: Threat Landscape, Malicious Libraries, Critical Vulnerabilities, OSINT, Foresight, CISO Control Checklist, and Sources.


  • SamHouston (Veracode)

    3. Threat Landscape

    Ransomware (30 days)

    Leak sites carried 1,127 victim claims in October, up 25.8% from 896 in September (HackerFeeds). N0n (154), The Gentlemen (143) and Qilin (140) posted 38.8% of them. These are criminals' own claims, not confirmed incidents; Ransomnews, which counts only verified attacks, has confirmed 878 for all of 2026 so far (single source).

    AI-run intrusions

    Microsoft's October 21 report is the clearest primary evidence this month: Storm-0940 used the ARTEX agentic penetration-testing framework to automate scanning, password spraying and OAuth application abuse, reaching privileged cloud access in some environments in under three hours. CrowdStrike separately documented groups running agentic intrusion campaigns and concluded that token budget, not engineering skill, limits their scale (single source, via Cybersecurity Dive).

    Identity

    In the run-up to the ConnectWise compromise, Microsoft recorded more than 151,000 failed sign-ins against 327 accounts at eight organizations between October 10 and 14, peaking near 2,900 per minute. Microsoft saw no successful logins in that phase; the successful access came afterwards, through the compromised ConnectWise application identities. Persistence was set by changing application credentials, which can survive the vendor disabling the original connection.

    Nation-state activity

    Beyond TraderTraitor and Storm-0940, Volt Typhoon has been using a relay network called Silent Train, built from rotating chains of compromised home-office, IoT and enterprise devices, to hide the origin of zero-day attacks (The Hacker News; SecurityWeek links it to Cisco SD-WAN zero-day exploitation). The Ivanti zero-day chain is attributed by Volexity to a cluster it tracks as UTA0576.

    Cloud and infrastructure

    Gheist shows the gap in GitHub's new safeguard: GitHub holds suspicious workflow runs only in public repositories, so private repositories and GitHub Enterprise Server ran Gheist's secret-dumping workflows, and Wiz then saw the same organizations' cloud credentials used against AWS Secrets Manager. A CVSS 10 flaw in Canonical LXD and MicroCloud (CVE-2026-112816) lets an attacker impersonate a trusted client.

    Expand Post
  • SamHouston (Veracode)

    4. Malicious Libraries and Components

    Confirmed means an official advisory or the original researcher's report. Single-source items are labeled.

    • testmetest campaign (18+ packages, Oct 19-25) | npm, GitHub — Credential-stealing worm (JFrog). Armed 42 repos from 11 owners with 12.9-13.7 MB payloads and hooks in Claude, Gemini, Cursor and VS Code settings; wipes the home directory if its stolen GitHub token is revoked. Confirmed. Action: Search repo trees directly, not GitHub code search. Remove persistence, then rotate GitHub, npm, cloud and AI-provider credentials.
    • Gheist (sync-check workflow) | GitHub Actions — Plants ci-sync-* branches that print base32-encoded secrets to logs, downloads them, deletes the run. 13,500+ branches, 850+ accounts (Wiz). Confirmed. Action: Hunt for ci-sync-* branches, commit 'ci: sync config', user agent gheist. Rotate every secret a hit repo could read.
    • anthropic.claude-code 2.1.312, 2.1.313 | Cursor Marketplace (IDE) — SSH backdoor with reverse tunnel and startup persistence (Cursor, Microsoft). Confirmed. Action: Check authorized_keys for svc-telemetry; isolate, clean or rebuild, then rotate.
    • sol-wallet-adapter, wallet-adapter-base, axelarjs-sdk, contracts-upgradeable, litecore-lib-ltc, @johnruff215-dev/solana-wallet-tracker | npm — Crypto-wallet-themed packages published as malware advisories in the last few hours (GitHub Advisory Database). Confirmed. Action: Block in package proxies; check lockfiles and build caches.
    • scdn-jquery, atlassian-wallboard-plugin, ms-client-portal, @axo_cuy/baileys, @bil-rgb/baileys, dsh-screenshot-native | npm — Further malware advisories published in the last 24 hours (GitHub). Confirmed. Action: Same as above.
    • wallet-tracking | PyPI — Malware advisory GHSA-8wmf-9cp5-g5hq, published today. Confirmed. Action: Block and check environments.
    • macs-shoaibs-pro17 | RubyGems — Malware advisory GHSA-625f-xj7r-qh7w, published in the last 24 hours. Confirmed. Action: Block and check environments.
    • dsh-redteam-mode 0.15.2 | npm — Flagged as malware by GitHub; Amazon Inspector reads it as offensive-security tooling (OSV MAL-2026-18366). Conflicting. Action: Remove unless deliberately approved.
    • indexed-btree | npm — Imitates sorted-btree; loader runs inside a normal method call, not at install (Checkmarx, via InfoWorld). Single source. Action: Remove; install-script blocking does not catch it.
    • Models using trust_remote_code | Hugging Face — Ship code that runs cryptominers and backdoors on GPU hosts (Pluto Security, via The Hacker News). Single source. Action: Disable trust_remote_code; pin and review models.
    • Searchjacked (319 extensions) | Chrome Web Store — Hijacks searches; 13.4M installs (Socket, via The Hacker News). Single source. Action: Enforce a browser-extension allowlist.

    No new Maven, NuGet, Go, crates.io or Composer malware reports were found today. GitHub's malware feed view shows only its 25 most recent advisories, so older entries in those ecosystems may exist.

    Expand Post
  • SamHouston (Veracode)

    5. Critical Vulnerabilities

    KEV dates and federal due dates were checked against CISA's catalog on November 2.

    • CVE-2026-109618, CVE-2026-109619 | PHP (PHP2Shell) — Unauthenticated remote code execution. Fix: PHP 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35. KEV Oct 26, due Oct 29.
    • CVE-2026-46300 | Linux kernel — Chains with PHP2Shell to plant webshells and run as root (CISA). Fix: Distribution kernel updates. KEV Oct 28, due Oct 31.
    • CVE-2026-111357, CVE-2026-118527 | Ivanti Connect Secure — Privilege escalation and file upload; zero-day chain with CVE-2026-104935. Fix: Ivanti fixes, then hunt. KEV Oct 30, due Nov 2 and Nov 13.
    • CVE-2026-97229 | GitLab CE/EE — Unauthenticated code execution via CI/CD regex. Fix: 19.5.1 and the other fixed releases. KEV Oct 29, due Nov 1.
    • CVE-2026-111497 | Google Brotli (Node2Shell) — Out-of-bounds write in the decoder; bundled in many runtimes. Fix: Brotli 1.0.10 / 1.1.1 / 1.2.1; Node.js 26.12.1 / 24.22.1 / 22.23.4. KEV Oct 27, due Nov 10.
    • CVE-2026-76418 | Cisco Secure Firewall ASA and FTD — Unauthenticated remote device reload (denial of service). Fix: Cisco fix. KEV Oct 29, due Nov 1.
    • CVE-2026-48356 | Adobe Commerce and Magento — Dangerous file upload leading to code execution. Fix: Adobe patch. KEV Oct 27, due Nov 10.
    • CVE-2026-41709 | VMware ESX — Admin actions can go unlogged. Fix: Broadcom fix. KEV Oct 28, due Nov 11.
    • CVE-2026-110447, CVE-2026-114625 | Collabora Online CODE; Arista VeloCloud Orchestrator — Command injection; SQL injection. Fix: Vendor fixes. KEV Oct 23, due Oct 26.
    • CVE-2026-102764 | BeyondTrust Remote Support — Authentication bypass; fresh probes reported Nov 2 (single source). Fix: Vendor fix. KEV Oct 16, due Oct 19.
    • CVE-2026-115560 | PHP — New RCE path, no patch; needs an unusual configuration. Fix: Set session.upload_progress.enabled=0 (PHP.net). Not in KEV.
    • CVE-2026-110264 | GitLab — CVSS 10 regex compiler flaw; no confirmed exploitation. Fix: Same GitLab releases as above. Not in KEV.
    Expand Post
  • SamHouston (Veracode)

    6. Underground and Leak Signals (OSINT)

    Leak-site and forum claims are UNCONFIRMED unless the named organization has confirmed.

    • UNCONFIRMED: N0n, October's most active leak-site group, named 38 maritime, port and logistics organizations with an October 19 deadline. None had confirmed a compromise as of October 29.
    • UNCONFIRMED: Leak-site listings posted today include Michigan State University (Byod), Holland & Knight (Redact) and Pertamina (RansomHouse).
    • SIGNAL: A Gentlemen ransomware affiliate known as Azazel reportedly stole ransom proceeds from about two dozen of the gang's victims (single source).

     

    7. Foresight: Next 2 to 6 Weeks

    Analyst assessment, not confirmed events.

    • Exploitation of PHP2Shell broadens to appliances and industrial products that embed PHP, and the kernel chain makes root compromise more likely where both are unpatched.
    • Developer tooling stays the main supply-chain target. In the past ten days researchers disclosed a trusted IDE marketplace serving a backdoored extension, a worm planting AI-assistant hooks in repositories, and mass secret theft from private CI. Expect copycats.
    • AI-run intrusions shorten response windows. Microsoft's under-three-hours finding means detections on OAuth application changes and service-principal sign-ins need to page someone, not wait for a daily review.
    • TraderTraitor will launder Binance proceeds for months; expect fake-recruiter lures aimed at engineers with production or wallet access.

     

    8. CISO Control Checklist

    • Patch PHP, Linux kernels, GitLab, Ivanti and Brotli-bundling runtimes; confirm the running version, not just the installed package. Tied to: KEV additions Oct 26 to 30. Owner: IT Operations and AppSec.
    • Hunt on Ivanti appliances after patching; do not rely on the Integrity Checker alone. Tied to: Ivanti zero-day chain. Owner: Security Operations.
    • Search all repos, including private and GHES, for ci-sync-* branches and unexpected AI-assistant or IDE config files. Tied to: Gheist, testmetest. Owner: Platform and DevOps.
    • Scope OIDC trust to protected branches; replace long-lived personal tokens with short-lived ones. Tied to: Gheist. Owner: Platform and Identity.
    • Allowlist IDE and browser extensions, including AI coding-assistant plugins, and pin their versions. Tied to: Cursor extension, Searchjacked. Owner: Endpoint and IT.
    • Block new malware-flagged packages at the package proxy, fed daily from OSV and GitHub advisories. Tied to: GitHub malware advisories. Owner: AppSec.
    • Review OAuth application credential changes and service-principal sign-ins from third-party apps. Tied to: Storm-0940 / ConnectWise. Owner: Identity and SOC.
    • Lock registrar accounts, monitor DNS and apply Subresource Integrity to third-party scripts on sensitive pages. Tied to: Polymarket / DebugBear. Owner: Web and Infrastructure.
    • Treat engineer laptops with production or wallet access as tier-0 assets. Tied to: Binance. Owner: Security Engineering.
    Expand Post
  • SamHouston (Veracode)

    Sources

    Main sources: CISA KEV catalog and alerts (Oct 26-30); PHP.net security advisories (Oct 21, 23); Node.js security releases (Oct 21); NIST NVD; FBI alert on Binance (Oct 31); TRM Labs (Oct 29); Microsoft Security Blog on Storm-0940 and ARTEX (Oct 21) and on the Claude Code extension (Oct 30); Cursor security notice (Oct 29); JFrog Security Research on testmetest (Oct 26); Wiz Research on Gheist (Oct 25); GitHub Advisory Database and OSV; Help Net Security, SecurityWeek, BleepingComputer, The Hacker News, The Register, CyberScoop, InfoWorld, Techzine, HackerFeeds and Ransomnews.

    Corroborate high-impact actions with your own telemetry and vendor advisories.

     

    This report is provided for informational purposes only and is not intended as legal, technical, or professional advice. While we strive for accuracy, Veracode does not warrant the completeness or accuracy of the information. Recipients should not rely solely on this report and must conduct their own thorough investigation and verification. Please work with your internal teams and relevant stakeholders to properly assess, implement, and remediate any identified threats or vulnerabilities. The information has been compiled from multiple sources, and Veracode assumes no liability for any errors, omissions, or actions taken based on this content.

    Expand Post

Topics (3)

No articles found
Loading

Ask the Community

Get answers, share a use case, discuss your favorite features, or get input from the community.