CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
‹Mon · 16 Nov 2026
All daily briefs →
Daily brief · UTC day

Monday, 16 November 2026

0 verified findings from 1 run · 1 update to prior coverage · the settled record for this UTC day, in the classic brief order.

Criticality

01Updates to prior coverage1 item

NOTABLEupdatedNATOB2

ARTEX: Microsoft reports Storm-0940, a China-state aligned actor, running an open-source multi-agent LLM penetration-testing framework against hundreds of organizations, with privileged cloud access in under three hours in some cases, and Expel sees the same infrastructure abuse Okta self-service registration

First published 2026-10-22 · open finding →

Updaterun 2026-11-16T0356Z-intelheadlinesummarytechniquessourcessourcing_note

The FBI's FLASH of 2026-11-13 says a variety of actors have used ARTEX since at least August against sectors including government, with more than 1,600 exposed consoles in early November. It lists the observed steps (cloud-trust and vendor-credential pivots, Kudu abuse, Active Directory credential theft, exfiltration preparation), the telemetry to check and the attack-surface hardening it recommends.

The FBI's FLASH of 2026-11-13 (TLP:CLEAR) adds a US authority's account of ARTEX use. It says a variety of malicious actors have used the framework since at least August 2026 against organisations in financial services, government, technology, defense, semiconductor, energy, healthcare, manufacturing, telecommunications and legal services, with some intrusions reaching privileged access in under three hours (FBI, 2026-11-13). The original repository was withdrawn on 2026-10-08, but forks, archived copies and a commercial version keep the framework available, and researchers identified more than 1,600 publicly exposed ARTEX consoles in early November (FBI, 2026-11-13). The FBI says ARTEX excels at finding and exploiting peripheral systems that get less security attention: partner and supplier portals, mobile backends, employee applications, legacy services and third-party integrations (FBI, 2026-11-13).

The FBI's table of observed activity lists these further steps. Initial access came through unsigned SAML assertions, XXE, SSRF, anonymous file upload, hard-coded administrator passwords in single-page-application JavaScript bundles, stolen VPN configurations and leaked credentials, cross-account cloud trust abused from an external partner tenant, and compromised third-party vendor credentials used across trusted B2B federation. Persistence used JSP and PHP web shells (one route was MySQL log poisoning), Kudu administrative APIs to run commands, and credentials added to existing OAuth applications. For privilege escalation and internal discovery the agents used Kerberoasting, DCSync, resource-based constrained delegation abuse and a cloud metadata query through XXE, ran iterative PowerShell enumeration against domain controllers (over 110,000 Active Directory objects), read LAPS passwords and inventoried Windows hosts without a particular EDR sensor; attempted lateral movement to domain controllers by pass-the-ticket, WinRM, Kerberos relay and pass-the-hash was blocked by endpoint protection. Theft preparation used database queries, mass blob reads, custom boot scripts via EC2 instances and new 100 GB volumes, with command output sent to rotating webhook endpoints, and command and control ran through residential proxies, Tor, Chisel and SoftEther (FBI, 2026-11-13).

Telemetry the FBI lists: unexpected outbound calls to LLM API endpoints (to be read alongside other suspicious activity), high-frequency sequential enumeration against login and search endpoints, Azure Resource Manager deployment-validation dry runs across many resource types, IAM permission tests with DryRun flags and sub-second test blob writes and deletes, credential additions to applications and service principals in the Entra audit log, and .aspx or .jsp files in unexpected web-application paths (FBI, 2026-11-13). Its recommendations: inventory every internet-facing application including the peripheral ones named above, restrict Kudu/SCM endpoints, cloud administration, hypervisor and backup interfaces to trusted networks or dedicated administrative paths, and disable basic publishing authentication where it is not required. For every Microsoft 365 tenant where an affected ConnectWise application is or was authorised, it asks for a review by application ID of activity from at least 2026-10-01 and says not to delete the enterprise application before evidence is preserved (FBI, 2026-11-13).

Verification & coverage notes1 run

2026-11-16T0356Z-intel · Sonnet 5.5 · window 26 h · 0 entries published

Verification & coverage notes

Window: gap 24.0 h (daily cadence, previous intel fire 2026-11-15T0356Z), window 26 h. A Sunday-to-Monday window: the newest item on every essential record is dated 2026-11-13 or earlier, no CISA KEV addition fell inside it (work/2026-11-16T0356Z-intel/kev-window.txt, catalogue 2026.11.13) and no covered CVE changed its ransomware flag. The outage-backfill duty did not apply (normal cadence).

Published: no new entry and one update record on 2026-10-22/artex-storm-0940-agentic-llm-pentest-spraying-oauth-abuse. The FBI's FLASH-2026-1113-001 (2026-11-13) gives a US authority's account of a variety of actors using ARTEX since at least August against sectors including government, and lists the observed steps (cloud-trust and B2B-federation pivots, Kudu abuse, Active Directory credential theft, exfiltration preparation) and the telemetry to check, none of which the entry carried. It cleared PD-11(d) as a development on covered ground; priority stays notable. The do-now ConnectWise application actions already sit on 2026-10-18/connectwise-cloud-backup-skykick-m365-app-credential-abuse, so actions[] did not change. Slice-completion check: every slice record of all four domains has a ledger row; no continuation was needed. state/coverage_backlog.md had no open row.

  • Single-source: none published as a new entry. The update rests on the FBI FLASH alone for its table; the entry's sourcing note says the FLASH consolidates the vendor reports it cites.
  • borderline-drop: PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25 (CVE-2026-6460 and 51 more), dropped on 2026-11-14 for "no public PoC"; the finder's write-up of 2026-11-09 now shows the crash step and a memory-disclosure step but not the code-execution step, the flaw needs a role that can create objects, no source reports exploitation and the fix is a scheduled minor release inside the regular cycle. Drop stands; the audit may revisit if exploitation or the missing step surfaces.
  • borderline-drop: Cyrus SASL SRP authentication bypass CVE-2026-129483; the SRP plugin is built only with --enable-srp (default off), no source names a product that ships it, no exploitation; upstream removed the plugin on master and no release has followed 2.1.28. Apache Shiro CVE-2026-129349, needs the non-default authenticationCachingEnabled on an LDAP realm and a known username, no exploitation.
  • borderline-drop: N-able N-central Hotfix 3 postponed (heise 2026-11-15, returned by S1 and S4); the entry already says a follow-up hotfix is planned and the stopgap is unchanged; N-able's own status page is a script-rendered shell no transport reads.
  • borderline-drop: Operation Endgame round of 2026-11-12 (Gootloader, CastleRAT, StealC; Europol and BKA), no Swiss participant and no technique content; the victim-notification channels are generic hygiene; also dropped on 2026-11-15.
  • borderline-drop: Proofpoint "Europe's Threat Landscape in 2026" and ENISA's 2026 State of Cybersecurity in the Union (both flagged ANNUAL REPORT); Proofpoint is trend statistics over behaviours the store already covers (device-code phishing, adversary-in-the-middle kits, webmail exploitation without a CVE for TA488) and its one Swiss datum is TA2730 lures aimed at brokerage customers; ENISA is a policy-level EU report outside Swiss jurisdiction with no technique content.
  • borderline-drop: Symantec's AI-assisted intrusions (US retailer; Orion RabbitMQ Erlang-cookie lateral movement); Symantec states the techniques are not new, one US victim, nothing a Swiss SOC would hunt differently; the AI thread is carried by the ARTEX, CyberStrikeAI and 3AM entries. Operation Snowball (Malbear Labs; Cisco BroadWorks XXE CVE-2026-20320, KEV 2026-11-10), Unit 42's CL-STA-1238 (Cairn) and Enea's SilentAir and GTPDoor, an unnamed European telecom with no Swiss customer, US-centred targets and Asian operators.
  • borderline-drop: KEV rows of 2026-11-09 to 2026-11-13 that no entry covers, Cisco BroadWorks CVE-2026-20320, GPUStack CVE-2026-102895, Openwave Webtop CVE-2026-111793, UnrealIRCd CVE-2026-114713. The earlier dispositions stand. Cisco's advisory v1.2 of 2026-11-13 says it has no direct evidence of active exploitation of BroadWorks; UnrealIRCd's maintainer now confirms exploitation (The Hacker News 2026-11-14, heise 2026-11-15), but it needs an IRC network with two or more linked servers and no constituency footprint appears.
  • borderline-drop: Quantum Systems QBase update-server compromise (sources of 2026-11-12 and 2026-11-13, no Swiss customer named, reports conflict on whether Bundeswehr systems received the file); Eichstätt municipal ransomware (no vendor or actor named, letters to residents the only new fact); Maileva, 22 million recipients (no actor, account misuse only, no Swiss client); Amadeus booking-display breach (no Swiss victim, root cause disputed); Fireworks AI incidents (US downstream victims, origin already in the Cursor entry); BundID credential stuffing (one community blog, no operator or press confirmation); Berlin Rhysida leak interview (one analyst's assessment, no new fact on the incident); outage-themed Microsoft 365 phishing (single report relaying a vendor social post, commodity lure, US observations, no confirmed compromise).
  • out-of-window: Saxony emergency-services pager exposure, heise 2026-11-12 and Spiegel 2026-11-11, window_hours=26; the 2026-11-13 verifier also removed it as below the incident floor and the 2026-11-15 fire dropped it.
  • borderline-drop: SAP Patch Day critical rows beyond the four CVSS 10.0 rows (authenticated or CSRF), Fortinet FG-IR-26-193 (CVSS 7.7, man-in-the-middle precondition), GitHub advisory database niche criticals, the Cisco ISE row, Vaud Grand Conseil interpellation 26_INT_155 (a member's questions, no finding), React Server Components CVE-2026-126187 (no exploitation or proof of concept; dropped on 2026-11-12, 2026-11-13 and 2026-11-15).
  • Next fire: Oracle's Critical Security Patch Update is due 2026-11-17 (pre-release notice of 2026-11-12: 652 patches; Fusion Middleware 53 unauthenticated rows up to CVSS 10.0, E-Business Suite 22 unauthenticated rows up to 9.8, Analytics up to 10.0). The 2026-11-17 and 2026-11-18 fires must read the release's risk matrices before dropping any row.
  • Candidate sources not added (the guide is about one per run; two added): darktrace-blog (feed lags the site), malbear-labs (no feed, first appearance), enea-insights (telecom-only relevance).
  • Source health: 320 records probed; two flagged. edoeb-ch-press is fixed (staleness limit set to its quarterly cadence). safeonweb-be stays flagged: the whole host answers HTTP 500, a server-side outage with nothing to repair, documented in its notes.
  • Process note: the reader pool is dead (402 on every key, 401 on the anonymous tier), so extract on a 403-walled host ends in a long chain of reader errors before it fails; the recipe notes record the mirrors and APIs that work instead.
  • Verification: three iterations, confirmed CLEAN (iterations 2 and 3, both independent cold passes, no truth or editorial finding). Iteration 1 found three real defects in the new section and fixed them: a superseded FBI instruction about ConnectWise restoration was dropped, the FLASH's own hardening levers were added, and the sector count was removed because the FLASH states none; its advisory (T1059.001, metadata-query grouping) was applied. Advisories left as they stand: the entry's summary and sourcing note are longer than the 1-3 and two-sentence standards after six records (the audit may tighten them), and T1074.002 is not mapped because the FLASH ties it to no named behaviour.
  • Coverage gaps: ico-uk (403 on every rung, Welsh mirror readable); sygnia (blocked on every transport); belden-psirt (403 on every transport); lab52 (feed reset, WebFetch 503, extract returned undated cards); safeonweb-be (host outage, HTTP 500); connectwise-trust-center (403, CNA commits API readable); databreaches-net (feed readable, article pages 403); previdian (listing and feed not sweepable).