01Check Point IKEv1 VPN auth bypass exploited since 7 May, actor assessed with medium confidence to use Qilin. CISA KEV, public PoC, apply sk185033. Check Point IKEv1 VPN auth bypass (CVE-2026-50751, CVSS 9.3) exploited in the wild since 7 May, a month before disclosure, against a few dozen targeted organizations. Check Point confirmed post-compromise activity associated with a Qilin ransomware affiliate in one case and assesses with medium confidence that the actor behind the exploitation is financially motivated and uses Qilin ransomware (Check Point, 2026-06-08). Unauthenticated session forgery on Remote Access / Mobile Access gateways. NCSC-CH flagged it as actively exploited (NCSC-CH, 2026-06-08) and CISA added it to KEV (CISA KEV catalog, 2026-06-08). →
02TeamPCP open-sources its Mini Shai-Hulud framework, spawning a new "Phantom Gyp" derivative. TeamPCP open-sources its Mini Shai-Hulud supply-chain framework on GitHub, spawning a new "Phantom Gyp" derivative and underscoring that valid SLSA provenance does not survive a subverted build environment (SANS ISC, 2026-06-08). →
03Exodus Intelligence publishes working exploit for a one-character Linux kernel nf_tables use-after-free (CVE-2026-23111). Working public exploit for a one-character Linux kernel nf_tables UAF (CVE-2026-23111), >99% reliable local-root and container escape across mainstream distros; patch shipped upstream 5 February (Exodus Intelligence, 2026-06-08). →
04Unit 42: Microsoft Teams external-chat now a primary phishing surface for APT29 and UNC6692. Microsoft Teams external chat is now ~42% of phishing alerts in Cortex, driven by APT29 (Cloaked Ursa) and UNC6692 IT-support impersonation, a configuration-hardening problem, not a patch (Unit 42, 2026-06-08). →
05CVE-2026-42271, BerriAI LiteLLM: low-privilege command injection to host RCE, added to CISA KEV. LiteLLM AI-gateway command injection (CVE-2026-42271) added to CISA KEV: host RCE via the MCP test endpoints, unauthenticated when chained with CVE-2026-48710; fixed in 1.83.7 (GitHub Advisory). →
Meta disclosed it detected and disrupted a new spear-phishing campaign linked to NSO Group's Pegasus operation, and filed a federal contempt-of-court complaint arguing the activity violates the 2025 permanent injunction barring NSO from targeting WhatsApp or its users (Meta, 2026-06-08; CyberScoop, 2026-06-08). The campaign used one-click links sent to WhatsApp users that redirected them to external attacker-controlled websites, the same social-engineering pattern (T1566.002) tied to earlier NSO phishing chains; Meta states no WhatsApp protocol zero-day and no end-to-end-encryption bypass was involved (BleepingComputer, 2026-06-08). Meta removed test accounts and groups NSO created on the platform.
Why it matters to us: The threat vector is user-level social engineering, not platform exploitation, iOS Lockdown Mode and Android Advanced Protection both reduce the Pegasus delivery surface, and mobile-threat-defence monitoring of device-integrity attestation is the relevant control. NSO's confirmed customer base is governments and its targeting pattern (officials, journalists, activists) is documented across EU member states, keeping commercial-spyware exposure a standing concern for public-sector mobile fleets.
The University of Oxford disclosed a breach after Group GTI, the third-party provider of the CareerConnect career-services platform, reported its systems were compromised on 28 May 2026 (BleepingComputer, 2026-06-08; Oxford Careers Service, 2026-06-01). Exposed data includes student first names, last names and email addresses; for users who do not authenticate via institutional Single Sign-On, encrypted passwords were also taken. CareerConnect is used by Oxford, King's College London and the University of Manchester among others, so the breach spans multiple UK higher-education institutions (BleepingComputer, 2026-06-08); The Register notes further unnamed UK and overseas institutions are affected (The Register, 2026-06-06). GTI assessed the intrusion as credential-harvest oriented, raising the likelihood of follow-on phishing against institutional email addresses.
UPDATE (originally covered 2026-06-06): A SANS ISC handler diary tracking the TeamPCP supply-chain campaign through 7 June reports the operators have open-sourced their Mini Shai-Hulud framework on GitHub, triggering a second wave of derivative campaigns (SANS ISC, 2026-06-08). Beyond the previously-covered Miasma worm, which compromised npm packages including Red Hat's @redhat-cloud-services scope (Wiz, 2026-06-01), the diary names a newly-tracked Phantom Gyp campaign that abuses node-gyp / binding.gyp install-time script execution in compromised npm packages; both inject malicious CI/CD hooks (SANS ISC, 2026-06-08).
The diary's load-bearing detection-engineering point: valid SLSA provenance attestations do not protect against supply-chain injection when the build environment itself is subverted from the inside. The recommended shift is from attestation-verification to build-pipeline integrity, monitor GitHub Actions runner process trees for unexpected outbound network from within a build, alert on actions/upload-artifact shipping signed-but-anomalous binaries, and cross-check published package checksums against CI logs via independent transparency ledgers (e.g. Sigstore Rekor). EU/Swiss public-sector teams running npm-based automation or Red Hat tooling should audit CI/CD pipeline definitions for unexpected workflow-step insertions.
The Miasma / Mini Shai-Hulud / Hades supply-chain worm (last seen backdooring @redhat-cloud-services packages and the TeamPCP "Phantom Gyp" framework) ran a fresh wave on 2026-06-24: 23+ malicious versions across the LeoPlatform and RStreams serverless-data-pipeline npm ecosystems (leo-sdk, leo-auth, leo-aws, leo-cli) after the czirker publisher account was compromised, plus a Go-module compromise of Verana Blockchain (Socket Security, 2026-06-25).
The wave reuses the previously documented binding.gyp/node-gyp install-time execution to stage a Bun runtime that harvests .env files, npm/GitHub/cloud tokens, SSH keys and IDE/AI-agent configs, scraping GitHub Actions CI secrets (JFrog, 2026-06-26), and again carries the RevokeAndItGoesKaboom campaign marker that Socket ties to the earlier codfish/semantic-release-action compromise (documented by StepSecurity), where the malicious action searched GitHub commit messages bearing that string as an operator dead-drop channel (Socket Security, 2026-06-25). Any CH/EU team consuming these packages in CI should rotate all exposed CI/cloud credentials since 2026-06-20 and alert on node-gyp evaluating JavaScript from binding.gyp.
Check Point disclosed and patched CVE-2026-50751 (CVSS 9.3) on 8 June 2026. It is a logic-flow weakness in certificate validation in the deprecated IKEv1 key exchange affecting Remote Access VPN and Mobile Access deployments. An unauthenticated remote attacker can establish a VPN session without a valid user password; post-authentication activity is still required to reach internal resources (Check Point, 2026-06-08). Check Point has observed exploitation since 7 May against a few dozen targeted organizations, with one case showing confirmed post-compromise activity associated with a Qilin ransomware affiliate. Based on the post-exploitation activity it observed, Check Point assesses with medium confidence that the actor behind the exploitation is financially motivated and uses Qilin ransomware (Check Point, 2026-06-08). NCSC-CH issued an advisory the same day flagging the CVE as actively exploited and linking observed exploitation to a Qilin ransomware affiliate (NCSC-CH, 2026-06-08); CISA added the CVE to its KEV catalog on 8 June (CISA KEV catalog, 2026-06-08). The companion CVE-2026-50752 (CVSS 7.4, site-to-site IKEv1 MitM under specific conditions, no observed exploitation) should be patched in the same window.
Triage: Check Point says to treat every completed Quick Mode exchange recorded before the fix as suspicious, and the discriminator it gives is a user or source IP address the organisation does not recognise (Check Point, sk185033).
An attacker can bypass user authentication by exploiting a logic flow weakness in the Remote Access and Mobile Access certificate validation and establish a remote access VPN connection without a valid user password
Check Point
Observed exploitation linked to Qilin ransomware affiliate.
NCSC-NL updated its advisory (NCSC-2026-0179, version 1.0.1) on 2026-06-16 to note that public proof-of-concept code is now available for the Check Point Security Gateway IKEv1 authentication bypass (CVE-2026-50751), increasing the probability of exploitation (NCSC-NL, 2026-06-16). NCSC-NL scores the two flaws at CVSS v4 6.9 and 6.3, against Check Point's 9.3 and 7.4 (NCSC-NL, 2026-06-16).
The flaw lets an unauthenticated client abuse the IKEv1 negotiation to bypass peer-signature verification and impersonate any VPN identity configured for certificate or mixed authentication (username/password-only configurations are not affected); watchTowr released its technical analysis and the PoC together on 2026-06-12 (Help Net Security, 2026-06-12). Apply the early-June Check Point hotfix; where feasible disable IKEv1 legacy mode or enforce mandatory machine-certificate authentication, which is not bypassable by this flaw.
The structured CVE data above marked the companion CVE-2026-50752 as exploited and in KEV instead of CVE-2026-50751. CISA listed CVE-2026-50751 on 2026-06-08 (CISA KEV catalog, 2026-06-08), and CVE-2026-50752 has no reported exploitation (Check Point, 2026-06-08).
The headline and summary also gave the Qilin link without its basis. Check Point has observed exploitation since 7 May against a few dozen targeted organizations. It confirmed post-compromise activity associated with a Qilin ransomware affiliate in one case and, separately, assesses with medium confidence that the actor behind the exploitation is financially motivated and uses Qilin ransomware (Check Point, 2026-06-08). NCSC-CH's advisory of the same day flags the CVE as actively exploited (NCSC-CH, 2026-06-08).
watchTowr released its technical breakdown and the proof-of-concept client together on 2026-06-12 (Help Net Security, 2026-06-12). Four of the nine affected branches, R80.20.X, R80.40, R81 and R81.10, are end of support, and Rapid7 advises organizations on them to prioritize migration to a supported release (Rapid7, 2026-06-08).
Check Point's hunt for CVE-2026-50751 is a search of gateway logs for completed IKEv1 Quick Mode exchanges ("Key Install" events marked Quick Mode completion) over at least 7 May to 5 June 2026. Any such event recorded before the hotfix or mitigation is to be treated as suspicious and inspected for unrecognised users or source IP addresses, and Check Point offers an IPS protection for the public proof-of-concept that adds visibility into attempts and scanning without remediating the flaw (Check Point, sk185033). The compromise lookback from 7 May follows that criterion.
CISA added CVE-2026-42271 to its KEV catalog on 8 June 2026, confirming active exploitation of a command-injection flaw in LiteLLM, the open-source AI gateway/proxy (CISA KEV catalog, 2026-06-08) (GitHub Advisory GHSA-v4p8-mg3p-g94g). Two preview endpoints, POST /mcp-rest/test/connection and POST /mcp-rest/test/tools/list, accept a full MCP server configuration (command, args, env) in the request body; with stdio transport, the proxy spawns the supplied command on the host under the proxy's privileges. The endpoints were gated only by a valid API key with no role check, so any authenticated user (including low-privilege internal keys) could execute arbitrary commands. Horizon3.ai documents that chaining with CVE-2026-48710 (a Starlette Host-header validation bypass) makes the path unauthenticated (Horizon3.ai, 2026-06-01). Affected: LiteLLM 1.74.2 to < 1.83.7; fixed in 1.83.7, which adds role-based authorization on the MCP test endpoints.
When called with a stdio configuration, the endpoints attempted to connect, which spawned the supplied command as a subprocess on the proxy host with the privileges of the proxy process.
LiteLLM 1.74.2 through 1.83.6 is affected and 1.83.7 fixes it, Starlette 1.0.0 or earlier makes the flaw reachable without authentication (Horizon3.ai, 2026-06-01), and the advisory's workaround is to block the two test endpoints at the reverse proxy or API gateway (GitHub Advisory GHSA-v4p8-mg3p-g94g).
Exodus Intelligence released a full technical write-up and working exploit for CVE-2026-23111, a use-after-free in the Linux kernel nf_tables subsystem caused by a single misplaced ! operator in nft_map_catchall_activate() that inverts the genmask check and skips inactive catchall elements during the abort path (Exodus Intelligence, 2026-06-08). Exodus reports >99% reliability on idle Debian Bookworm/Trixie and Ubuntu 22.04/24.04 LTS, yielding unprivileged-local-user to root escalation and container escape (T1068, T1611) (The Hacker News, 2026-06-08). The flaw was patched upstream on 5 February 2026; distro packages are shipping the fix (Ubuntu Security, rated 7.8). No network-reachable path exists; exploitation requires local access or code execution inside a container, making this high-value post-exploitation tooling for shared compute (Kubernetes nodes, CI/CD runners, multi-tenant VMs).
Why it matters to us: With a reliable public exploit now available, the patch gap is the exposure. Apply vendor kernel updates containing the 5 February upstream fix; in container environments enforce seccomp and AppArmor/SELinux profiles that restrict nf_tables syscalls for untrusted workloads. Detection concepts: anomalous UID transitions to 0 from non-root parents (Linux audit execve/setuid records); unexpected privileged process spawns inside containers.
Unit 42 reports that collaboration-platform phishing reached 42% of all phishing alerts in Cortex in the first four months of 2026, up from 30% in the preceding period, with Microsoft Teams external messaging the dominant vector (Unit 42, 2026-06-08). Two clusters dominate: Cloaked Ursa (APT29 / Midnight Blizzard) uses previously-compromised M365 tenants (often small-business accounts) to stand up IT-support-styled domains, then sends Teams messages requesting MFA approval or credential re-entry under an account-maintenance pretext. UNC6692 floods inboxes to manufacture urgency, then poses as IT support over Teams, ultimately delivering the SNOW suite, SNOWBELT (browser-extension backdoor), SNOWGLAZE (WebSocket tunneler) and SNOWBASIN (persistent backdoor), after dumping LSASS via Task Manager (T1003.001) and moving laterally with Pass-the-Hash (T1550.002) (Mandiant, 2026-04-23). The root enabler is the default Teams configuration permitting unrestricted external-tenant messaging.
Why it matters to us: Hardening is configuration, not patching, restrict external access in the Teams Admin Center to explicitly-allowed partner domains and disable unmanaged/consumer-account chat. Detection concepts: Entra ID sign-in logs for logons originating from external M365 tenants; Teams activity logs for ExternalUserJoined events followed by rapid file/link shares; MDI alerts on MFA anomalies after cross-tenant contact. Extend AiTM-aware Conditional Access to Teams sign-in contexts.
Microsoft Threat Intelligence documents a campaign by Storm-3075 (initial-access broker) and Fox Tempest (malware-signing-as-a-service operator) that weaponises public enthusiasm for AI tools, impersonating ChatGPT, Claude, DeepSeek and Microsoft Copilot through SEO poisoning, malvertising and multi-stage redirection chains (Rebrandly → CAPTCHA gate → credential-harvesting landing) (Microsoft, 2026-06-08). Downloaded binaries are code-signed with certificates obtained through Fox Tempest's MSaaS operation (T1553.002), suppressing initial detection; payloads include Lumma Stealer, Vidar, Hijack Loader and Oyster, with fraudulent GitHub repositories used for payload staging. Microsoft's separate analysis details the Fox Tempest malware-signing-as-a-service operation that supplies the certificates (Microsoft, 2026-05-19).
Why it matters to us: Code-signing is no longer a trust anchor here; a valid Authenticode signature on a fresh "AI tool" installer is consistent with this chain. Detection concepts: Sysmon EID 1 for browser-parented processes spawning infostealer-family command lines; EDR process-injection alerts for Hijack Loader. Phish-resistant MFA (FIDO2/passkeys) removes the downstream AiTM credential-replay value even when an endpoint is seeded.
Patch Check Point IKEv1 VPN gateways now (CVE-2026-50751): apply hotfix sk185033, disable deprecated IKEv1 remote-access support or enforce machine-certificate authentication, and review gateway logs from 7 May 2026 for completed IKEv1 Quick Mode ("Key Install") events before the fix that come from unrecognised users or source IP addresses.
Apply kernel updates for CVE-2026-23111 and harden container syscall policy; a >99%-reliable public LPE/container-escape exploit is now available; ship the 5 February upstream fix and enforce seccomp/AppArmor restrictions on nf_tables for untrusted workloads.
2026-06-09-40d562df· Claude Opus 4.8 · 9 entries published
Items dropped:
Luna Moth / UNC3753 physical-USB extortion escalation (Mandiant GTIG, 2026-06-05), substantively the same campaign and physical-intrusion development already given a full deep dive on 2026-06-06; no material new delta this run beyond the corroborating Security Affairs write-up (2026-06-08). Excluded under the no-repetition rule.
ICO £963,900 fine of South Staffordshire Water (Cl0p), primary enforcement action dated 2026-05-11, ~4 weeks outside the 36 h window; no genuine in-window publication (a sitemap lastmod of 2026-06-02 is not a new article). Out-of-window: primary source 2026-05-11.
EU Council TTE meeting (CSA2 high-risk supplier framework / NIS2 simplification progress); the 2026-06-09 meeting tables progress reports already captured in the 2026-W23 weekly policy section; no operational defender delta. Logged as horizon item, not re-reported.
CNIL €5M fine of IQVIA (health-data warehouses); the underlying decision is dated 2026-05-28, outside the 36 h window; the only in-window hook was a corroborating article whose URL did not resolve to the IQVIA story, so the PD-7 fresh-development carve-out no longer holds. Dropped on recency. May resurface if genuine in-window reporting appears; the precedent (CNIL rejecting a "pseudonymous = anonymous" SRB defence) remains relevant to Swiss/EU health-data processors.
Avcon Jet (Austria) Qilin ransomware listing, sourced only to cybernews and a vendor blog (dexpose), no victim disclosure or HIGH-reliability journalism; leak-site-claim posture fails the fake-news guard. The Qilin/edge-VPN-targeting angle is retained on Check Point's HIGH-reliability attribution in § 5.
CVE-2026-8037 / CVE-2026-33691 (Progress Kemp LoadMaster), dropped after verification: the only available citation (the Progress Customer Community bulletin) renders client-side and returns a portal/error shell rather than stable bulletin content, and BSI's WID-SEC-2026-1812 advisory page has the same SPA limitation. With no citable stable source for a no-ITW, no-PoC vulnerability, the item did not meet the citation bar. Worth re-checking next run if Progress publishes a stable bulletin URL or a secondary source covers it.
Single-source / reduced-confidence:
SoFi Securities (Hong Kong) third-party vendor breach, single-source (BleepingComputer with SoFi spokesperson confirmation), scope and data categories still under investigation, weak CH/EU and public-sector nexus. Held back pending corroboration; may resurface if a regulator notice or scope detail lands.
Contradictions: none surfaced this run.
Sub-agents: S1–S4 all returned within budget (Claude Sonnet 4.6). No stalls.
Coverage gaps: databreaches-net (persistent 403, no usable Wayback snapshot, breach stories covered via BleepingComputer/CyberScoop/The Record); inside-it-ch (persistent 404, 5+ runs); sophos-xops (503 streak, 4+ runs); sec-disclosures-edgar (no qualifying 8-K Item 1.05 filings in window); edpb, us-treasury-ofac (no in-window cyber decisions/designations); shadowserver, greynoise, wiz-blog, vulncheck (S1 not independently queried, coverage cross-checked via NVD/ENISA EUVD/CISA KEV); elastic-seclabs, dfirreport, intel471, kaspersky-securelist, checkpoint-research (most recent items outside the 36 h window).
Unmatched action items (migrated)
Lock down Microsoft Teams external access: restrict external messaging to allow-listed partner domains and disable unmanaged/consumer-account chat to close the APT29/UNC6692 social-engineering surface; extend AiTM-aware Conditional Access to Teams sign-in. See § 3.
Audit CI/CD pipeline definitions: TeamPCP derivatives (Miasma, Phantom Gyp) inject build-time hooks that pass SLSA provenance; review GitHub Actions workflow steps and monitor runner process trees for unexpected outbound network. See § 4.