CUTSIGNcutting for sign — daily OSINT threat read

2026-11-04

34 stories analyzed · 4 deep reads · brief: “[PIPELINE] Cyber Threat Brief — 2026-11-04”

received 2026-11-04 12:41Z · emailed 2026-11-04 13:00Z

29
new IoCs
37
novel behaviors
7
story updates
9
watch devs 48h
9
verdict cards
× closeNew IoCs (29) — by story
× closeNovel behaviors (37) — by story
× closeStory updates (7) — developments of earlier briefs' stories

↓ Jump to brief cards

Today: 34 stories in the brief, 7 high-priority. Top story: Siemens IoT2050 Node-RED flaw CVE-2026-58115 exploited to drop Linux bot and webshell flows. 7 are developments of stories already being tracked. 5 tracked stories escalated in the last 48 h.

Developments on tracked stories (48 h)

Hackers actively exploit SSHole OpenSSH flaw (CVE-2026-123158) to gain root on Linux systems, confirmed by CISA KEV listing · 3 developments
  • 2026-11-09 17:10Z GreyNoise recorded 16 successful exploitation chains from six IPs with post-exploitation behavior, including a root attacker installing the TAC Agent Python C2 implant (C2 tac.vpnla[.]org, never tasked) and Chinese-language implant strings. OpenSSH fixed the flaw in 10.6p2 on November 5, and Previdian confirmed exploitation from 13 IPs in nine countries. Title revised: "Hackers actively exploit SSHole OpenSSH flaw (CVE-2026-123158) to gain root on Linux systems". source
  • 2026-11-09 17:10Z CVE-2026-123158 was added to CISA's Known Exploited Vulnerabilities catalog. source
  • 2026-11-09 15:12Z The article details the root cause (musl crypt() returning * with salt borrowing), fixed OpenSSH 10.6p2 and per-branch Alpine package versions, and states that as of Nov 6 neither OpenSSH nor Alpine reports exploitation, with CISA marking exploitation status as poc. It also gives exposure checks and mitigations, and notes that the Alpine tiny-cloud alpine account is affected. Title revised: "OpenSSH SSHole (CVE-2026-123158) password auth bypass on musl/Alpine; PoC public, exploitation unconfirmed". source
Attackers probing SAP NetWeaver honeypots for webshells left by CVE-2025-31324; no confirmed compromises stated · 1 development
  • 2026-11-09 15:31Z Public repo for CVE-2021-44228: palantir/log4j-sniffer — A tool that scans archives to check for vulnerable log4j versions (★205; verify before trusting — fake PoCs are common). source
OpenSSH on musl flaw (*sshole) lets oversized passwords log into password-disabled accounts; exploited in the wild; patch to 10.6p2 · 2 developments
  • 2026-11-09 18:15Z New reporting headline states hackers are exploiting the *sshole OpenSSH flaw to breach Linux systems, contradicting the earlier claim that sources did not report observed exploitation. Confirmed in-the-wild exploitation is a material change for hunters. source
  • 2026-11-09 15:32Z An index-page headline reports that hackers targeted the OpenSSH "SSHole" flaw within hours of disclosure and gained root on a honeypot. This contradicts the stored summary's statement that no exploitation had been observed. source
Google patches Chrome zero-day CVE-2026-125350 (XML use-after-free) exploited in the wild; no public exploit details · 1 development
  • 2026-11-10 19:32Z CVE-2026-125350 was added to CISA's Known Exploited Vulnerabilities catalog. source
Barracuda confirms exploitation of ESG flaws CVE-2026-116606 and CVE-2026-111560 giving root access at a small number of organizations · 2 developments
  • 2026-11-10 19:32Z CVE-2026-111560 was added to CISA's Known Exploited Vulnerabilities catalog. source
  • 2026-11-10 19:32Z CVE-2026-116606 was added to CISA's Known Exploited Vulnerabilities catalog. source

From the brief — 17 verdict-shaped cards

P1

Siemens IoT2050 Node-RED flaw CVE-2026-58115 exploited to drop Linux bot and webshell flows

HighCVE-2026-58115update to 2026-11-03IoC cardAI verdict card

Since Oct 30, 2026, VulnCheck has observed attackers exploiting CVE-2026-58115, a CVSS 10 missing-authentication flaw in the Node-RED HTTP interface on Siemens SIMATIC IoT2050 Advanced devices. A single HTTP request deploys and auto-triggers a malicious flow that runs a shell wrapper using wget (curl fallback) to fetch a Linux bot to /dev/shm/.b or /tmp/.kworker and execute it. Other requests plant persistent webshells: an HTTP in endpoint (e.g. /cmd) wired to an exec node that runs commands from a query parameter. SecurityWeek reports VulnCheck called the exploitation successful; hunt for wget/curl/sh spawned by the Node-RED process, hidden files in /dev/shm and /tmp, and unexpected exec nodes or HTTP endpoints in deployed flows.

EXPOSURE CHECK
AffectedSiemens SIMATIC IoT2050 Advanced running Industrial OS with Node-RED installed, versions before 4.3.4.1
Only ifNode-RED installed · Node-RED HTTP interface/editor reachable without adminAuth
Not affected ifNode-RED uninstalled · adminAuth/credential or OAuth authentication enabled on editor and admin API · version 4.3.4.1 or later
Fixed in4.3.4.1

Why it matters: Actively exploited CVSS 10 with concrete huntable behaviors, but niche ICS/Node-RED product, less common in financial enterprise estates. (raised to P1: exploited + behaviors/KEV)

P1

Russia-aligned Gorbag (UAC-0226) exploits WinRAR CVE-2025-8088 to deploy BeautyStealer against Ukraine

Highactor: Gorbag (UAC-0226, SHADOW-EARTH-066)malware: BeautyStealer / GIFTEDCROOK, Prime ReverseShellCVE-2025-8088update to 2026-11-03IoC cardAI verdict card

ESET reports Gorbag, a Russia-aligned actor overlapping with CERT-UA's UAC-0226, targeting Ukrainian law enforcement, local government and defense entities via spearphishing. Since early 2026 it delivers RAR archives exploiting CVE-2025-8088 that show a decoy PDF while dropping a Startup-folder LNK, an encrypted payload and a PowerShell loader in %ProgramData%; earlier chains used XLSM macros dropping BeautyStealer into %ProgramData%. BeautyStealer harvests browser credentials/cookies, VPN configs and documents, exfiltrates via Telegram sendDocument or a FastAPI C2, then self-deletes. Hunt for WinRAR writing LNKs into Startup, PowerShell loaders in %ProgramData%, and Telegram API traffic from non-browser processes.

EXPOSURE CHECK
AffectedWinRAR versions vulnerable to CVE-2025-8088 (patched July 2025)
Only ifUser opens crafted RAR archive on Windows with vulnerable WinRAR
Not affected ifWinRAR updated with the July 2025 fix

Why it matters: Exploited WinRAR flaw with concrete huntable chain, but targeting is Ukraine-specific, not financial. (raised to P1: exploited + behaviors/KEV)

P1

WordPress Core CVE-2026-119977 TOCTOU race enables unauthenticated code execution during upgrade; added to CISA KEV

CriticalCVE-2026-119977AI verdict card

CISA's KEV catalog lists CVE-2026-119977, a WordPress Core TOCTOU race condition that could let unauthenticated attackers execute code on the server during full-package core upgrades, exploiting predictable web-accessible staging paths. The KEV entry, dated 2026-11-03 with a due date of 2026-11-06, requires forensic triage under BOD 26-04 and is the basis for the brief's claim of confirmed exploitation. The sources reviewed do not describe specific attacker behavior, payloads, or IoCs, so hunters should focus on web-accessible staging/upgrade directories and unexpected code execution during core updates.

EXPOSURE CHECK
AffectedWordPress Core (vulnerable versions per Wordfence advisory: 4.7.0 through 7.1.3 per advisory slug wordpress-core-470-713)
Only ifFull-package core upgrade performed, creating web-accessible staging paths during the upgrade window
Not affected ifCore is at a fixed version (7.1.4 or later per vendor release note)
Fixed in7.1.4

Why it matters: KEV-listed unauthenticated RCE in WordPress Core, a commonly deployed internet-facing product, with a mandated forensic triage requirement.

P1

C3RB3R ransomware attacks target Synology DSM NAS devices; attempts to deliver ransomware via patched DSM flaws, no confirmed compromise count stated

Highactor: C3RB3Rmalware: C3RB3R ransomwareCVE-2024-10441CVE-2024-50629CVE-2024-10445CVE-2026-13684CVE-2026-13639update to 2026-11-03AI verdict card

Synology says threat actors exploited a DSM vulnerability patched in December 2024 (advisory SA_24_20, listing CVE-2024-10441, CVE-2024-50629, CVE-2024-10445) to target devices running outdated DSM, with customers reporting C3RB3R ransomware locking files with a .L0CK3D extension. Qihoo 360 links C3RB3R to two DSM flaws (CVE-2026-13684, CVE-2026-13639) it says were fixed in September 2026, and sources report ransom notes named read-me3.txt dropped in encrypted directories. Hunters should look for .L0CK3D file extensions, read-me3.txt files, and unexpected shell or ransomware activity on DSM hosts running outdated versions.

EXPOSURE CHECK
AffectedSynology DiskStation Manager (DSM) 7.2.2 before 7.2.2-72806-1 · DSM 7.2.1 before 7.2.1-69057-6 · DSM 7.2 before 7.2-64570-4 · DSM 7.1 before 7.1.1-42962-7 · DSM 6.2 before 6.2.4-25556-8
Fixed inDSM 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4, 7.1.1-42962-7, 6.2.4-25556-8 or above

Why it matters: Actively exploited internet-facing NAS platform with ransomware impact and concrete file-level artifacts to hunt for.

P1

Europe-wide supermarket refrigeration attacks via Copeland XWEB controllers; UK meat suppliers caught in second wave, no attribution

HighAI verdict card

Unidentified attackers remotely altered supermarket and grocery refrigeration controls across Europe in a second wave following a first wave in France, causing stock to spoil in some cases. The Record reports three UK meat suppliers and a UK fruit and vegetable wholesaler were hit via internet-exposed Copeland XWEB supervisory controllers, with an authentication bypass in firmware 1.12.1 and earlier, for which an update had been available since August. Hunters should look for exposed XWEB controllers and unexpected remote defrost-mode changes; no group has claimed or been attributed.

EXPOSURE CHECK
AffectedCopeland XWEB supervisory controllers / XWEB monitoring solutions, firmware 1.12.1 and earlier
Only ifController exposed to the internet
Fixed inFirmware newer than 1.12.1 (exact fixed version not stated in source)

Why it matters: Actively exploited internet-exposed OT/IoT controllers with confirmed physical impact; patch and exposure checks warrant action today.

P1

OpsShield cPGuard update channel hijacked to push malicious root script to customer servers

HighAI verdict card

Attackers used compromised credentials to reach OpsShield's update CDN and billing/licensing server, then uploaded a fake cPGuard update signed with a stolen access key. Versions 5.88.12–5.88.19 were served for roughly 70 minutes, and OpsShield estimates 2,950 servers executed the malicious script as root and about 7,900 client account records were copied. Hunters should look for a hidden root shell and temp-folder files left by the update, unexpected SSH keys, and cPGuard updates from versions 5.88.12–5.88.19; OpsShield has released 5.88.25 and later, which remove these artifacts.

EXPOSURE CHECK
AffectedcPGuard versions 5.88.12–5.88.19 (OpsShield)
Only ifServer polled OpsShield update infrastructure during the compromise window (about 70 minutes)
Not affected ifcPGuard was not online during the compromise window, per OpsShield
Fixed in5.88.25

Why it matters: Supply-chain compromise of widely deployed Linux hosting security agent with confirmed root execution on customer servers.

P1

Linux kernel IPv4 TCP use-after-free CVE-2026-98432: Red Hat fixes shipped, Ubuntu fixes in testing, no confirmed exploitation

HighCVE-2026-98432update to 2026-11-03AI verdict card

A use-after-free in the Linux kernel's IPv4 TCP code, tracked as CVE-2026-98432, can be triggered remotely and unauthenticated by SYN requests carrying IPv4 Record Route or Timestamp options to a listening TCP port, potentially leading to RCE. Red Hat shipped fixed kernels for RHEL 8, 9 and 10 on November 1 and published an nftables interim mitigation, while Ubuntu fixes remain in the opt-in -proposed pocket. The source states no vendor, CERT, or kernel CVE team has reported attacks, and a proof-only GitHub crash PoC exists that does not implement code execution. Hunters should watch for inbound IPv4 TCP SYNs with IP options to listening ports and check kernel versions against the fixed builds.

EXPOSURE CHECK
AffectedLinux kernel IPv4 TCP path, present since Linux 4.4 (RHEL 8, 9, 10 and Ubuntu 22.04, 24.04, 26.04 per source)
Only ifServer accepts IPv4 TCP connections on a listening port · Attacker can send IPv4 TCP SYN packets with Record Route or Timestamp options; IPv6 main path not affected
Not affected ifIPv6 main path is not affected per source · Standalone exposure reduced by nftables drop rule for IPv4 TCP packets with IP options (partial mitigation; traffic between containers on same host can bypass)
Fixed inRHEL 8: 4.18.0-553.182.1.el8_10 (RHSA-2026:93414); RHEL 9.8: 5.14.0-687.64.1.el9_8 (RHSA-2026:93412); RHEL 10.2: 6.12.0-211.72.1.el10_2 (RHSA-2026:93413); Ubuntu fixes only in -proposed (22.04: 5.15.0-203.213, 24.04: 6.8.0-149.149, 26.04: 7.0.0-43.43)

Why it matters: Remote unauthenticated kernel RCE class flaw in widely deployed Linux, with public proof-only PoC and a stated vendor-acknowledged RCE; patches available for RHEL but Ubuntu unpatched.

P2

Google/Mandiant: LLMjacking via stolen cloud tokens and API keys drives $100K+/day AI charges

Mediumactor: UNC6993CVE-2026-40217update to 2026-11-03IoC card

GTIG and Mandiant describe multiple 2026 incidents where actors (including UNC6993) used stolen IAM credentials, service account keys, GitHub PATs, session tokens and leaked LLM API keys to enable LLM services (Bedrock, Gemini API), create keys and service accounts, inject SSH keys, and resell access via LLM Mixers such as Jet Night and newapi[.]pro. Charges exceeded $100,000 in a day and reached ~$1M cumulatively at some victims, including financial services. One cluster exploited LiteLLM CVE-2026-40217 to elevate virtual keys to PROXY_ADMIN. Hunt cloud audit logs for unexpected LLM service enablement, access/service-account key creation, burn-and-rotate service account churn, project/instance SSH key metadata changes, GPU quota requests, and max_tokens=1 key-validation sweeps.

EXPOSURE CHECK
AffectedLiteLLM gateway (CVE-2026-40217, /key/regenerate) — versions not stated · Publicly exposed Ollama endpoints · Cloud accounts with LLM services (AWS Bedrock, Gemini API) reachable via leaked keys
Only ifCloud credentials, service account keys, PATs, session tokens or LLM API keys exposed or stolen · LLM endpoints publicly accessible without auth

Why it matters: Concrete cloud-audit-log huntable behaviors in common cloud/LLM platforms affecting financial sector; no single mass-exploited perimeter product.

P2

BTCPay Server hot wallets drained of about $1.62M via flaw in versions 2.4.1 and earlier

High

BTCPay Server, a self-hosted cryptocurrency payment processor, says attackers stole Bitcoin and Litecoin from hot wallets on servers running 2.4.1 or earlier, and Bitquery reports about $1.62M (18.38 BTC and 3,405 LTC) across 682 sweeps. The sources do not name the exploited vulnerability or describe the attacker's on-host actions; they say the earlier August issue exposed .macaroon files, but it is unclear if the new attacks are related. Hunters should look for unexpected outbound wallet sweeps from hot wallets on BTCPay instances and treat older servers as compromised, using the published wallet addresses for matching.

EXPOSURE CHECK
AffectedBTCPay Server 2.4.1 and earlier
Only ifRunning a BTCPay Server instance with hot wallets on the server
Not affected ifRunning BTCPay Server 2.4.7 or later
Fixed in2.4.7

Why it matters: Confirmed cryptocurrency theft from internet-facing self-hosted payment software, but no concrete on-host behaviors are published.

P2

APT29 Watering-Hole Campaign Exploits Patched Apple and Chrome Flaws to Deliver Info-Stealers

Highactor: APT29CVE-2024-27834CVE-2025-43529CVE-2026-20700CVE-2025-14174CVE-2025-43510CVE-2025-43520CVE-2026-3910CVE-2025-27038

Sekoia attributes with moderate-to-high confidence a watering-hole campaign to APT29 that used compromised legitimate sites and lookalike domains, plus a tampered Plerdy SEO tracker loaded by thousands of Ukrainian-heavy sites between August 27 and September 3. Injected JavaScript profiled visitor devices and browser versions, after which the C2 server pushed platform-specific n-day exploit chains. The sources report no confirmed compromises and say Apple and Google have patched the targeted flaws; hunters should look for visits to the named compromised or lookalike domains and the injected Plerdy tracker script.

EXPOSURE CHECK
AffectediOS 16.7 (CVE-2024-27834, CVE-2025-43529) · iOS 18.5 (CVE-2025-43529, CVE-2026-20700, CVE-2025-14174, CVE-2025-43510, CVE-2025-43520) · Chrome for Android 139 to 145, excluding 143 (CVE-2026-3910, CVE-2025-27038)
Only ifVisiting a compromised or lookalike site serving the injected JavaScript
Not affected ifDevice runs patched iOS or Chrome for Android builds per Apple and Google fixes

Why it matters: Actively exploited n-day chains on mobile browsers, but patched and no concrete endpoint behaviors or detections published, so hunt rather than act today.

P2

Attackers attempt to exploit unpatched CryptoPayment Gateway WordPress plugin flaw CVE-2026-81648 (no confirmed compromises stated)

MediumCVE-2026-81648update to 2026-11-03AI verdict card

Defused Cyber reports in-the-wild exploitation attempts against CVE-2026-81648, a CVSS 10.0 unauthenticated authorization flaw in the CryptoPayment Gateway WordPress plugin, versions 1.2.1 through 1.2.2, which has no known fix and was closed on the WordPress Plugin Directory. The flaw is an unauthorized AJAX endpoint that allows deleting arbitrary files, overwriting the payment gateway configuration, and recovering stored wallet credentials in cleartext. The attack traffic reportedly came from infrastructure marketing itself as 'Anonymous KYC-Free VPS Hosting', but the sources do not print specific indicators or log patterns. Site owners are advised to remove the plugin, rotate wallet keys, and audit for suspicious changes.

EXPOSURE CHECK
AffectedCryptoPayment Gateway WordPress plugin versions 1.2.1 through 1.2.2
Only ifPlugin installed on the WordPress site

Why it matters: Unpatched critical WordPress plugin under attempted exploitation, but no concrete huntable behaviors or indicators are printed and the install base is unclear.

P2

Binance attributes $6.34B theft to North Korea-linked compromise of three engineers' machines via fake recruiting, tampered Homebrew, and internal AI tool abuse

Highactor: TraderTraitor (FBI attribution, disputed by North Korea)

Binance's initial incident report says attackers ran a months-long campaign starting June with a tampered Homebrew download, then a September fake job interview leading to a malicious coding assignment that installed undetected malware. Attackers used the infected machine and an internal AI tool on October 20 to take over two engineers' systems, then deployed a container using a token from the first engineer to reach the wallet signing service and move hot-wallet assets, including abuse of EIP-7702 delegations. Hunters should look for unexpected package-manager installs of developer tools, malicious repository execution, container deployments using engineer tokens, and EIP-7702 authorizations; the FBI attributes the theft to TraderTraitor, a claim North Korea rejects.

Why it matters: Concrete intrusion chain with huntable developer-endpoint and container behaviors, but largely a single vendor-reported incident with limited published detection content.

P2

Chainstack discloses production breach exposing customer account data and password hashes; node credentials treated as exposed

Medium

Blockchain infrastructure provider Chainstack disclosed that an external attacker entered via a third-party component, reached a development environment on October 26, 2026, and then pivoted into parts of production. The company says the intrusion was detected and access cut on October 31, 2026, and that a database with organization names, account holder names, member emails and password hashes was accessed. Chainstack says there is no evidence node credentials were read but treats them as exposed; defenders should hunt for the access path, and customers are advised to rotate node credentials and API keys and reset passwords.

Why it matters: Customer data breach with a vendor-stated access path but no published technical behaviors, IoCs, or detection guidance.

P2

WorkOS says attacker used ARTEX AI framework to breach internal sales app; no confirmed production or app data access

MediumIoC cardVerdict card

Developer platform WorkOS disclosed unauthorized access to an internal application used by its sales team, identified on October 30, 2026, where the attacker took business contact records, customer account histories, and summaries of customer communications. The company says the attacker used the ARTEX AI offensive security framework to automate reconnaissance and exploitation attempts, and that no WorkOS app data or production services were affected. Hunters should look for web requests bearing the user agents 'artex-enrich/1.0' and 'norma/0.4', and recipients of the company warned about phishing and social engineering using the exposed contact data.

EXPOSURE CHECK
Not affected ifNo WorkOS app data or production services were accessed or affected, according to the company

Why it matters: Reported breach with a concrete huntable user-agent indicator tied to an AI pentest framework, but no confirmed exploited vulnerability or enterprise-deployed product compromise.

P2

Android November 2026 updates patch over 200 vulnerabilities, including critical Framework RCE CVE-2026-58868

HighCVE-2026-58868update to 2026-11-03

Google's November 2026 Android security bulletins fix more than 200 flaws across two patch levels (2026-11-01 and 2026-11-05). The most severe is CVE-2026-58868, a critical Framework component issue that the vendor says could lead to remote code execution without user interaction or additional execution privileges. The sources describe no observed exploitation and print no detection artifacts, so hunting guidance is limited to confirming devices are at patch level 2026-11-05 or later.

EXPOSURE CHECK
AffectedAndroid Framework component (CVE-2026-58868), devices prior to security patch level 2026-11-05
Not affected ifDevices at security patch level 2026-11-05 or later
Fixed in2026-11-05 security patch level

Why it matters: Critical unauthenticated RCE in Android Framework patched; no exploitation reported in sources, so patching is the action rather than hunting.

P2

Barracuda appliance flaws CVE-2026-116606 and CVE-2026-111560 can be chained to root; no exploitation reported

MediumCVE-2026-116606CVE-2026-111560

Barracuda disclosed a pre-authentication authorization bypass (CVE-2026-116606, CVSS 9.3, Email Security Gateway only) and a command injection flaw (CVE-2026-111560, CVSS 8.6, across several products) that together could let an attacker bypass authorization and obtain root. Exploitation requires access to the administrative interface, so exposure depends on whether admin interfaces are reachable from the internet. The source reports no exploitation; hunters should focus on admin-interface access logs and firmware currency rather than specific attack artifacts.

EXPOSURE CHECK
AffectedBarracuda Email Security Gateway (CVE-2026-116606 and CVE-2026-111560) · Barracuda Load Balancer Application Delivery Controller (CVE-2026-111560) · Barracuda Message Archiver (CVE-2026-111560) · Barracuda WAF Control Center (CVE-2026-111560) · Barracuda Web Application Firewall (CVE-2026-111560) · Barracuda Web Security Gateway (CVE-2026-111560)
Only ifAttacker must have access to the administrative interface of the affected product
Not affected ifAdministrative interfaces are not exposed to the internet, per Barracuda's guidance that such organizations are less vulnerable

Why it matters: Chained root path on commonly deployed email/web security appliances, but no exploitation reported and admin-interface access is required.

P3

Microsoft: fake cracked-software installers bundle WorldProxyPool proxyware, BOINC and adware

Lowmalware: OfferLoaderIoC card

Microsoft Threat Intelligence reports a fake-download campaign using trojanized Inno Setup-style installers (cracked software, games, executors) that deliver multiple monetization 'offers': WorldProxyPool proxyware, CharityEngine/BOINC compute software, and AW Manager/Windows Manager adware. Microsoft confirmed installations on affected devices, including WorldProxyPool SYSTEM scheduled tasks. Hunt for eld*.exe/set_*.exe executing from %TEMP%\is-*.tmp\, HTTP callbacks containing d=inno&r=offer_execution, and new WorldProxyPool* scheduled tasks or unexpected BOINC/VirtualBox installs.

EXPOSURE CHECK
AffectedWindows endpoints where users run trojanized Inno Setup-style installers from cracked-software/game/utility lure sites
Only ifUser downloads and executes a fake cracked-software or unofficial installer
Not affected ifMicrosoft Defender PUA protection / cloud-delivered protection blocks offers (failed offers report r=offer_execution_fail)

Why it matters: Commodity PUA/proxyware bundling via user-run cracked software; low severity but concrete huntable artifacts and published queries.

Also in today's read (17)

Priorities and summaries are drawn from public reporting only. The analyst view carries the full behaviors, evidence and indicators.