Security daily

Synthesized by Clarity (Claude) from 33 sources · May contain errors — spot one? [email protected] · Methodology →

Anonymous 'Bikini' Lands 9 CVEs, Second Wave Due This Week

Sources
33
Words
1,020
Read
5min

Topics AI Regulation Agentic AI LLM Inference

◆ The signal

The quote that should define your new threat model: 'You do NOT need a SOTA model.' Recalibrate your assumptions about attacker capability and prepare for the promised second wave of disclosures this week.

◆ INTELLIGENCE MAP

Intelligence map

  1. 01

    AI-Fuzzed Mass 0-Day Drop Kills Responsible Disclosure

    act now

    Bikini used GPT-5.5-3-Codex-Spark to fuzz 15 OSS projects and published PoCs with zero vendor notification. 9 CVEs confirmed, second wave imminent. Adobe and Oracle both accelerated patch cadence citing AI-driven exploit discovery. The capability is now commodity — harness quality matters more than model frontier.

    15
    OSS projects with 0-days
    3
    sources
    • CVEs confirmed
    • Projects affected
    • Vendor notification
    • Second wave ETA
    1. 01Linux KernelUnpatched
    2. 02PHPUnpatched
    3. 03OpenVPNUnpatched
    4. 04FFmpegUnpatched
    5. 057-ZipUnpatched
    6. 06Gitea/GogsUnpatched
  2. 02

    Three Active Exploitation Campaigns: SimpleHelp, FortiBleed, Perimeter Appliances

    act now

    SimpleHelp CVE-2026-48558 is dropping TaskWeaver/Djinn stealer via OIDC bypass. FortiBleed harvested creds from 86K+ Fortinet devices for INC ransomware. Chrome Longinus and Kemp LoadMaster have patches but narrow windows. NetScaler's 6 new flaws include a CitrixBleed-class SAML parser bug (CVE-2026-8451) on gear with 20+ KEV entries.

    86,000+
    Fortinet devices harvested
    4
    sources
    • FortiBleed devices
    • NetScaler CVEs
    • NetScaler KEV history
    • EvilTokens surge
    1. FortiBleed devices86,000
    2. Azure CLI attempts81,000,000
    3. NetScaler CVSS8.8
    4. EvilTokens growth1380%
  3. 03

    Software Factories Auto-Merge 20–60% of PRs Without Human Review

    monitor

    Warp's Oz platform, Cursor's cloud agents, and OpenAI Codex are converging on 'software factories' that auto-merge up to 60% of PRs with no human gate. Agents now hold GitHub/Jira/Slack tokens and accept instructions from ticket bodies — turning your issue tracker into an executable injection surface. CEO predicts this becomes standard by mid-2027.

    60%
    PRs auto-merged
    4
    sources
    • Auto-merge rate
    • Standard by
    • Cursor FDE scale
    • Eager adopters
    1. PR auto-merge rate (high end)60
  4. 04

    AI Toolchain Shadow Data Flows: Covert Telemetry and Stealth Model Routing

    monitor

    Claude Code shipped undisclosed telemetry since March (timezone, proxy, lab affiliation) — only reversed after public exposure. Meituan's 1.6T-param LongCat-2.0 served as 'Owl Alpha' on OpenRouter (top-3 by volume) routing developer prompts to an undisclosed Chinese provider. OmniRoute aggregates 236 AI providers via local proxy with zero governance.

    236
    AI providers via proxy
    5
    sources
    • Claude Code telemetry
    • OmniRoute providers
    • Meituan model params
    • Sonnet 5 platforms
    1. Mar 2026Claude Code telemetry begins
    2. Jun 2026Owl Alpha unmasked as Meituan
    3. Jul 1Sonnet 5 default across 7+ platforms
    4. Jul 1OmniRoute ships 236-provider proxy
  5. 05

    US-Iran Kinetic Conflict Raises Iranian APT Retaliation Risk

    background

    Active US/Israel-Iran military conflict with stalled Qatar negotiations. Iranian cyber attacks on Israel already tripled YoY (1,600→4,800 incidents in June). Historical pattern: kinetic conflict precedes APT33/34/35 retaliation against US energy, financial, and CI targets. Markets price peace; your detection engineering should not.

    3x
    Iranian attacks YoY
    2
    sources
    • Iran attacks Jun
    • YoY increase
    • Prior year Jun
    • Diplomacy status
    1. Iran attacks Jun 20251600baseline
    2. Iran attacks Jun 20264800+200%

◆ DEEP DIVES

Deep dives

  1. 01

    Three Active Exploitation Campaigns Hitting Your Perimeter Right Now

    act now

    The Situation

    Three distinct campaigns are exploiting perimeter infrastructure today — not disclosed, not theoretical, actively compromising systems. They require different responses but share one trait: every target sits at your edge with privileged network position and minimal endpoint detection coverage.


    Campaign 1: SimpleHelp CVE-2026-48558 → TaskWeaver/Djinn

    SimpleHelp's OpenID Connect implementation has an authentication bypass (CVE-2026-48558) that's being exploited in the wild to drop the TaskWeaver loader and Djinn infostealer. Patches have been available since May — this is a known-unpatched window being swept. Any OIDC-enabled RMM server is in scope, including MSP-managed instances you don't directly control.

    If your MSP runs SimpleHelp, their compromise is your compromise. Verify their patch status today, not next review cycle.

    Campaign 2: FortiBleed — 86,000+ Devices Harvested

    An INC ransomware affiliate deployed on-firewall credential sniffers across 86,000+ Fortinet devices, harvesting credentials transiting the perimeter. This was only discovered because the attackers left an open directory exposed. There is no single patch — this requires credential rotation for every account whose traffic transited an affected device, plus forensic audit of firewall configs for injected processes.

    Campaign 3: Perimeter Appliance Patches With Closing Windows

    VulnerabilityProductStatusAction
    CVE-2026-6307 (Longinus)Chrome V8Patched 106.0.5249.119Force-update fleet within 48h
    CVE-2026-8037Kemp LoadMasterPatched 7.2.63.2Patch before WatchTowr PoC weaponizes
    CVE-2026-8451NetScaler ADC/GatewayPatched (6 flaws)Same SAML class as CitrixBleed — rush

    The Chrome Longinus flaw deserves special attention: it achieves full RCE and renderer-sandbox escape through a single V8 JIT primitive — no memory spraying, no exploit chaining. That lowers the weaponization skill floor dramatically. NetScaler's CVE-2026-8451 is the same out-of-bounds SAML parsing class that produced CitrixBleed in 2023, on appliances carrying 20+ CISA KEV entries.


    The Azure CLI Spray — Context, Not Crisis

    An automated password spray generated 81M+ login attempts against Azure CLI, breaching at least 78 accounts. CLI/programmatic authentication paths frequently sit outside Conditional Access and MFA policy envelopes — the gap being exploited is a configuration omission, not a vulnerability.

    Action items

    • Patch all SimpleHelp instances with OIDC enabled and hunt for TaskWeaver/Djinn IOCs on RMM infrastructure, including MSP-managed servers
    • Force credential rotation and MFA re-enrollment for all accounts whose traffic transited Fortinet perimeter devices; audit firewall configs for injected sniffers
    • Push Chrome to 106.0.5249.119+ fleet-wide via enterprise policy and patch Kemp LoadMaster to 7.2.63.2 before public weaponization
    • Patch NetScaler ADC/Gateway and manually adjust HTTP/2 timeout (patch alone doesn't fix the DoS); rotate sessions post-patch
    • Extend Conditional Access + MFA to all Azure CLI and programmatic sign-in paths; disable legacy authentication

    Sources:AI-fuzzed 0-day dump hits your OSS stack while SimpleHelp & FortiBleed are already live · Patch NetScaler now + hunt for ARToken in your M365: two active threats in today's feed · Two items on the wire. First: 81 million Azure CLI login attempts against the cloud edge · Your unpatched edge: libssh2 & Gitea 0-days dropped raw, Chrome Longinus + Kemp RCE need patching now

  2. 02

    The Bikini Dump: AI-Assisted Mass 0-Day Production Is Now Commodity

    act now

    What Happened

    An anonymous actor using the handle 'Bikini' published a repository called 'exploitarium'. It carries working PoC exploits for 15 widely-deployed open-source projects. No vendor coordination. Nine CVEs are confirmed. A second wave is promised this week. The affected list reads like a software bill of materials:

    • Linux kernel, PHP, OpenVPN, Libssh2, FFmpeg
    • 7-Zip, VLC, Ghidra, Gitea, Gogs
    • MyBB, AnyDesk (and more)

    Why This Is Different

    The method is the story. Bikini says he fuzzed the codebases with OpenAI's GPT-5.5-3-Codex-Spark, then verified findings by hand. I cannot confirm a model by that name exists, so treat the tooling claim as reported, not established. His stated point cuts against the 'only frontier AI is dangerous' line:

    "You do NOT need a SOTA model to help you identify these issues... my data seems to show that it is only marginal when paired with decent human oversight and a good harness."

    The claim: mass-producing 0-days now needs a decent harness and human oversight, not a frontier model. Semgrep's own numbers point the same way. Their pipeline scored 53–61% F1 against GLM 5.2's 39% and Claude Code's 32% on IDOR detection. Integration engineering beats raw model capability. Those figures are vendor-reported.

    Industry Response Is Already Confirming the Shift

    Two vendors changed behavior. Adobe shifted to semi-monthly patching and Oracle moved to monthly releases, both citing AI-powered exploit discovery. Apple expedited WebKit patches and said it did so because AI compresses the disclosure-to-exploit window. A monthly patch SLA now sits structurally behind the threat.


    Cross-Source Contradiction Worth Noting

    One tension runs through today's reporting. Anthropic says Sonnet 5's 'cyber safeguards' are hardened, and the US government is export-controlling models on offensive-cyber capability scores. Bikini says frontier models aren't required. The regulatory framework is aimed at the last war: commodity models with good harnesses are the threat, not frontier models behind vendor guardrails.

    Action items

    • Inventory exposure to all 15 Bikini-dump projects across fleet, container images, and CI pipelines; map to the 9 confirmed CVEs and prepare compensating controls before the second drop
    • Recalibrate patch SLAs for internet-facing and client-side software from weeks to days, matching the AI-compressed disclosure-to-exploit reality
    • Restrict SSH exposure for libssh2 and isolate Gitea Docker behind auth-proxy/VPN; deploy hunts for anomalous SSH crashes and unauthorized Gitea admin actions
    • Build or acquire AI-assisted fuzzing capability for your own critical codebases before adversaries apply this methodology to your exposed attack surface

    Sources:AI-fuzzed 0-day dump hits your OSS stack while SimpleHelp & FortiBleed are already live · Your unpatched edge: libssh2 & Gitea 0-days dropped raw, Chrome Longinus + Kemp RCE need patching now · AI just collapsed your n-day patch window — Apple's emergency WebKit push is the warning shot

  3. 03

    Software Factories and AI Supply-Chain Governance: The Controls You're Missing

    monitor

    The Auto-Merge Problem

    Multiple sources converged this week on a single architectural shift: 'software factories' that auto-merge 20–60% of pull requests with no human reviewer. Warp's Oz platform is live. Cursor is scaling Forward Deployed Engineers 10x. OpenAI's Alexander Embiricos said the quiet part: the goal is connecting agents to 'review and deploy... that's how you help it land much more work.'

    The control assumption this breaks is fundamental: human code review is silently embedded in your SOC 2 change-management evidence, your detection engineering, and your intuition about what ships to production. When 60% of PRs merge without a human, that control doesn't degrade — it evaporates.


    The Shadow Data Flow Problem

    Simultaneously, the AI toolchain itself is leaking data through channels your governance doesn't cover:

    ToolUndisclosed BehaviorData at Risk
    Claude CodeCovert telemetry since March (timezone, proxy, lab affiliation)Developer context, routing metadata
    OpenRouter 'Owl Alpha'Meituan's 1.6T Chinese model serving as stealth top-3 providerAll prompts/code routed via auto-select
    OmniRouteLocal proxy aggregating 236 AI providers with no code changesSource, secrets, prompts to unvetted third parties
    Sonnet 5 (7+ platforms)Autonomous browser/terminal execution, default for all Free/Pro usersCodebase, infra, credentials accessible to agent
    A top-tier AI vendor shipped covert telemetry into our developers' tools for four months undetected — assume every cloud-connected AI assistant is an untrusted supply-chain component until its egress is proven.

    The Convergence

    These aren't separate problems. The software factory writes and merges code via AI agents that route through AI providers you didn't vet, using credentials you didn't scope, transmitting data through channels you didn't document. The entire chain from prompt injection → agent execution → auto-merge → production is live today. The buyer is the engineering leader, not the practitioner — meaning this lands via a leadership deal before security is consulted.


    Where Sources Agree

    Every source covering this theme agrees: adoption is outpacing governance. Only 10–20% of enterprise staff are enthusiastic adopters, but the 'champion' model ensures they're the ones wiring agents into your repos. Kent Beck's framing cuts cleanly: 'We're failing to accumulate trust at the same rate as new code is accumulated.'

    Action items

    • Draft an 'autonomous code agent' policy requiring human approval on any PR touching auth, secrets, IaC, CI config, or dependency manifests — enforce via CODEOWNERS and branch protection by end of sprint
    • Inventory Claude Code, Cursor, Copilot, and OmniRoute usage via egress monitoring (not procurement records) and block or gate any undocumented telemetry channels
    • Treat all AI agents as first-class non-human identities: dedicated service accounts, scoped/short-lived tokens, and SIEM logging for agent-initiated commits and deploys
    • Disable stealth/preview model routing on OpenRouter and any auto-routing AI gateways; pin approved, provenance-verified models only
    • Mandate SAST, SCA, and secrets scanning on all agent-authored PRs with no exemptions; tag AI-generated commits distinctly for audit and incident response

    Sources:Auto-merged PRs at 60%: the AI 'software factory' just broke your human-review control · Cursor's 'software factory' wants agents deploying to prod · Your devs' Claude Code was covertly exfiltrating telemetry · Your Claude Code and OpenRouter pipelines are leaking provenance · Sonnet 5's terminal + browser autonomy is already in your dev stack

◆ QUICK HITS

Quick hits

  • ARToken/EvilTokens BEC-as-a-service surged 1,380% in early 2026 — bypasses MFA on M365 via AiTM session theft; hunt for suspicious inbox rules and OAuth consents now

    Patch NetScaler now + hunt for ARToken in your M365: two active threats in today's feed

  • Azure CLI password spray hit 81M+ attempts and breached 78 accounts — CLI auth paths frequently sit outside Conditional Access policy; extend MFA coverage immediately

    Two items on the wire. First: 81 million Azure CLI login attempts against the cloud edge

  • Apple expedited WebKit patches and publicly stated AI compresses the disclosure-to-exploit window — push iOS/macOS updates fleet-wide via MDM within 72 hours

    AI just collapsed your n-day patch window — Apple's emergency WebKit push is the warning shot

  • ClickFix shifted to API-driven delivery with 3,000+ live payloads — static IOC detection is now stale; deploy behavioral rules for clipboard-paste-to-PowerShell and browser-spawned interpreters

    Two items on the wire. First: 81 million Azure CLI login attempts against the cloud edge

  • 47-day TLS certificate lifetimes confirmed by 2029; AWS shipped native ACME support in Certificate Manager — begin automation pilot now or inherit outage-driven fire drills

    47-day TLS certs are coming — automate now or your SOC inherits outage-driven fire drills

  • Higgsfield shipped Seed Audio 1.0: voice cloning across 18 languages via API — mandate out-of-band callback verification for all wire transfers and privileged requests

    Sonnet 5 just became the default agent on your endpoints — and 18-language voice cloning shipped the same day

  • Update: Fable 5/Mythos 5 export controls lifted after Commerce-brokered deal — but Amazon researchers' jailbreak (vulnerability discovery on demand) proves vendor guardrails are not a security boundary

    Amazon researchers jailbroke Anthropic's Fable — your LLM guardrails aren't a control

  • Update: PQC timeline converges — Microsoft, Google, and Cloudflare all target 2029 for post-quantum crypto migration, accelerated from prior estimates; aligns with the Dec 2030 federal mandate

    AI-fuzzed 0-day dump hits your OSS stack while SimpleHelp & FortiBleed are already live

  • Aflac Japan attackers maintained 10-day dwell (June 15–25) and exfiltrated 4.38M records including 230K bank-transfer records — benchmark your own SaaS exfil MTTD against this

    Your unpatched edge: libssh2 & Gitea 0-days dropped raw, Chrome Longinus + Kemp RCE need patching now

  • Iranian cyber attacks on Israel tripled YoY to 4,800 incidents in June amid active US-Iran kinetic conflict — elevate detection for APT33/34/35 TTPs if you're in energy, finance, or CI sectors

    US-Iran war is live: your SOC should be at elevated alert for Iranian APT retaliation

◆ Bottom line

The take.

AI just commoditized mass 0-day production — 15 core OSS projects got PoC exploits dropped with zero vendor coordination using a non-frontier model and a good harness, while SimpleHelp and FortiBleed are actively exploiting your perimeter right now and 'software factories' are auto-merging 60% of code without human review. Your patch SLA, your human-review assumption, and your AI toolchain trust model all broke this week.

— Promit, reading as Security ·

Frequently asked

Who is 'Bikini' and why does the nine-CVE dump matter beyond the raw count?
'Bikini' is an anonymous researcher who published the 'exploitarium' repository with working PoCs against 15 widely-deployed open-source projects including the Linux kernel, PHP, OpenVPN, libssh2, FFmpeg, 7-Zip, Ghidra, Gitea, and AnyDesk. Nine CVEs are confirmed and a second wave is promised this week — with no vendor coordination, meaning defenders and attackers get the PoCs simultaneously.
What does 'you do NOT need a SOTA model' actually change about the threat model?
It shifts the risk driver from model capability to integration engineering. Bikini claims a decent fuzzing harness plus human oversight produced these bugs, and Semgrep's pipeline scoring 53–61% F1 versus frontier models at 32–39% on IDOR detection supports the pattern. Export controls and vendor guardrails aimed at frontier models miss the real threat: commodity models wrapped in good tooling.
Which items from the dump have no patch available, and what compensating controls apply?
libssh2 and Gitea both dropped as raw 0-days with no vendor timeline. For libssh2, restrict SSH exposure at the network layer and hunt for anomalous SSH client crashes. For Gitea, place Docker deployments behind an authenticating proxy or VPN and alert on unauthorized admin actions. Isolation is the only available control until vendors ship fixes.
How should patch SLAs change in response to AI-compressed disclosure-to-exploit windows?
Move internet-facing and client-side software SLAs from weeks to days. Adobe shifted to semi-monthly patching, Oracle moved to monthly cycles, and Apple expedited WebKit releases — all explicitly citing AI-accelerated exploit discovery. If your SLA is slower than the vendor's release cadence, your window of exposure is structurally widening every cycle.
What should defenders do before the promised second wave lands this week?
Complete an exposure inventory across the full 15-project list — fleet endpoints, container base images, and CI pipelines — and map it against the 9 confirmed CVEs. Stage compensating controls (network isolation, WAF rules, egress restrictions) for the projects you cannot patch immediately, so when new PoCs drop you are triaging known exposure rather than discovering it.

◆ Same day, different angle

Read this day as…

◆ Recent in security

Keep reading.

Spot an error? [email protected]