Why Fed and Treasury leaders Powell, Bessent just rushed into a critical cyber-risk meeting

Why Fed and Treasury leaders Powell, Bessent just rushed into a critical cyber-risk meeting

Treasury Secretary Scott Bessent and Fed Chair Jerome Powell convened an urgent meeting with Wall Street leaders this week, bypassing the routine briefing cadence and pulling bank CEOs into a direct conversation about AI-driven cyber risk.

Reports noted that the meeting aimed to ensure banks understood the risks posed by Mythos and similar models and were already taking defensive steps.

When the Treasury secretary and the Fed chair jointly pull bank chiefs into an urgent room, they are communicating that the risk is systemic.

The irony running through this episode is sharp.

On Mar. 2, the Treasury, State, and HHS moved to stop using Anthropic products, acting on a presidential directive, with Bessent publicly stating that Treasury was terminating all use.

On Mar. 9, the General Services Administration terminated Anthropic’s government-wide contract. On Apr. 8, a federal appeals court declined to block the Pentagon’s blocklisting of Anthropic while litigation continues.

So, in the same week, officials were managing an active procurement and national security dispute with Anthropic, while also warning the country’s largest banks to prepare for the risk posed by Anthropic-class capabilities.

What Mythos actually changed

The evidentiary basis for the official alarm rests on Anthropic’s own materials, which are more specific than typical model launch claims.

Anthropic says Mythos has found thousands of high-severity vulnerabilities, including flaws in every major operating system and every major web browser, and that more than 99% of them are still unpatched.

The company’s system card describes the model as capable of identifying and exploiting zero-days across those platforms. This is the kind of capability that, in the wrong hands or released without coordination, compresses the timeline between vulnerability discovery and weaponized attack.

Anthropic’s response to its own findings was to restrict access under a structure it calls Project Glasswing, limiting release to launch partners including Amazon Web Services, AppleBroadcom, Cisco, CrowdStrike, Google, JPMorganthe Linux Foundation, Microsoft, Nvidiaand Palo Alto Networks, plus more than 40 additional organizations that build or maintain critical software infrastructure.

Anthropic committed up to $100 million in usage credits and $4 million in donations to open-source security organizations as part of the effort.

The company also says it briefed US officials and key stakeholders before release, which means the Treasury meeting reflected an informed official judgment grounded in advance disclosure.

Anthropic claim / factWhy it matters to banks and regulators
Thousands of high-severity vulnerabilities foundSuggests capability is not theoretical or narrow
Flaws found in every major operating systemImplies broad attack surface across shared infrastructure
Flaws found in every major web browserExpands exposure beyond one vendor or one stack
More than 99% still unpatchedRaises urgency around defense timelines
Model can identify and exploit zero-daysCompresses the gap between discovery and weaponization
Access restricted under Project GlasswingSignals even Anthropic viewed release as high risk
40+ additional infrastructure organizations involvedShows concern extends beyond one company to core software ecosystems
Advance briefings to U.S. officialsSuggests the Treasury/Fed response was informed, not reactive theater

Banks are at the center of this concern because they depend on the broader software stack.

Treasury’s January 2025 Financial Services Sector Risk Management Plan identifies cloud concentration, software supply chains, and emerging technologiesincluding AI, as top sector riskswarning that reliance on common vendors and software creates conditions for cascading failures.

Banks share cloud providers, software vendors, payment rails, and clearing systems across the sector. A cyber capability that can efficiently find and exploit unpatched zero-days across every major operating system can hit an interconnected financial system with compounding force.

In this landscape, shared infrastructure means a single class of vulnerability can reach every node simultaneously.

The policy track making this an inevitability

On Feb. 18, Treasury announced a public-private initiative explicitly designed to develop practical tools for financial institutions to manage AI-specific cybersecurity risks.

On Mar. 23, Treasury and the Financial Stability Oversight Council launched an AI Innovation Seriesstating that insights from it would inform Treasury and FSOC work on reinforcing resilience and financial stability as AI embeds itself across core financial functions.

The Federal Reserve’s July 2025 cybersecurity report listed assessing AI risksbolstering cloud resilience, and exercising cyber-incident response plans among its joint FBIIC/FSSCC priorities.

Washington had also been building the conceptual framework for longer than that.

In June 2024, Treasury and FSOC hosted a conference on AI and financial stability. At it, then-Secretary Yellen identified opacity, inadequate risk management, and concentration among model vendors, data providers, and cloud providers as channels through which AI could create systemic vulnerabilities.

The FSB’s November 2024 AI report then codified four main systemic-vulnerability channels: third-party dependencies and service-provider concentration, market correlations, cyber risks, and model, data, and governance failures.

The IMF had separately found that cyberattacks on financial firms account for nearly 20% of all incidents it studiedand that the size of extreme losses had grown to $2.5 billion.

Mythos forced officials to operationalize a risk framework they had spent nearly two years constructing.

CryptoSlate Daily Brief

Daily signals, zero noise.

Market-moving headlines and context delivered every morning in one tight read.

DateInstitutionEventWhy it matters
Jun. 2024Treasury / FSOCConference on AI and financial stabilityEstablished early systemic-risk framing
Jun. 2024YellenWarned about opacity, weak risk management, and concentrationIdentified core vulnerability channels
Nov. 2024FSBAI report on systemic-vulnerability channelsInternational policy codification
Jan. 2025TreasuryFinancial Services Sector Risk Management PlanNamed cloud, supply chain, and AI as top risks
Jul. 2025Federal ReserveCybersecurity reportIncluded AI risk, cloud resilience, and incident exercises
Feb. 18, 2026TreasuryPublic-private AI cyber initiativeShift from theory to tools
Mar. 23, 2026Treasury / FSOCAI Innovation Series launchedLinked AI adoption to resilience and stability
Apr. 2026Treasury / FedUrgent bank CEO meetingOperationalized the framework

ScenarioTriggerPolicy responseImpact on banks
Bull caseGlasswing works, vulnerabilities get patched, access stays controlledContinued closed-door coordination, limited new rulesBanks treat this as a resilience drill
Base caseMore concern, but no visible incidentMore guidance, more exams, more vendor reviewsHigher compliance and patch-management pressure
Bear caseMore models show similar offensive capabilityTighter supervisory expectations, software provenance rules, incident reporting pressureGreater operational burden and faster control changes
Tail riskMaterial disruption tied to shared software/cloud exposureCrisis-style coordination across Treasury, Fed, regulatorsMarket confidence and operational continuity become key concerns