Security.io Daily Headlines — Monday, September 21, 2026
Five equally weighted developments: what happened and the leadership decision each creates.
Listen to today’s episode
Listen to the edition’s five developments and leadership decisions.
Episode transcript
5 developments · Executive decision contextThis is Max Vogal from Security.io with today’s Daily Headlines for Monday, September 21, 2026. Here are the top five security developments shaping today’s decisions—what happened, why each matters now, and the leadership action to consider.
CrowdSec disclosure joins package compromise, offboarding and source-code loss
What happened
Treat CrowdSec's disclosure as an identity and software-supply-chain incident, not merely a code leak. Validate developer offboarding, OAuth-token governance, repository-clone visibility and secret exposure together. On May 11, 2026, CrowdSec says 42 TanStack packages were backdoored with the credential-harvesting malware Shai Hulud.
The leadership decision
Security leaders should disable residual developer, contractor and leaver access across code, cloud and package platforms. Assign the incident owner across identity, developer platform, endpoint and application-security teams. A single-team response risks closing one access path while leaving cloud tokens, package credentials or copied secrets usable elsewhere.
AgentCore test turns prompt injection into a credential-boundary decision
What happened
Inventory every AgentCore Harness, restrict allowedTools, separate credentials from agent-visible runtime memory and prove command and egress telemetry before production use. On September 18, 2026, Unit 42 published a controlled test of credential exposure through Amazon Bedrock AgentCore Harness.
The leadership decision
Security leaders should inventory every AgentCore Harness and its allowedTools configuration. Pause production approval for harnesses whose tool, identity and egress boundaries cannot be demonstrated. This is an authority-governance issue, not a request for another generic prompt filter. Require AI platform owners to document the model, tools, credential providers, downstream services, runtime privilege and emergency-disable path for each production agent.
RatHat converts Android permissions into banking and identity exposure
What happened
Treat suspected RatHat infection as a mobile identity incident. Isolate the phone, revoke sessions and credentials, preserve evidence and rebuild from a trusted state. RatHat combines sideloading, Android accessibility abuse, Wireless Debugging and an AI-directed interface navigator to pursue banking credentials, authentication codes and device unlock secrets.
The leadership decision
Security leaders should block Android sideloading and unmanaged accessibility permissions where policy permits. Direct mobile, identity and fraud teams to use one escalation path. RatHat's target set spans device control, financial credentials and authentication material, so fragmented ticket handling can leave active sessions or recovery channels exposed.
Gyazo disclosure exposes authentication and image metadata at scale
What happened
Inventory corporate Gyazo use, reset affected credentials, revoke relevant sessions and X integrations, and assess whether exposed image metadata reveals sensitive business content. On September 16, 2026, Gyazo published its notice confirming unauthorised access and external exposure of user information and image metadata.
The leadership decision
Security leaders should discover corporate Gyazo accounts through SSO, browser, proxy and expense records. Treat Gyazo as a potentially unmanaged third party until organisational use is measured. Procurement records alone may miss individual accounts, browser extensions or screenshots shared through other collaboration systems.
EtherHiding shifts malware detection from domains to code and chain activity
What happened
Hunt for unexpected blockchain RPC traffic from browsers, editors and Node.js processes, then verify repository integrity where developer tools execute configuration automatically. Fresh on-chain measurement and a government incident analysis show EtherHiding operating as durable malware infrastructure across public blockchains and as a hidden execution path inside a developer repository.
The leadership decision
Security leaders should hunt for unexpected blockchain RPC traffic from developer processes. Direct application security, endpoint and threat-intelligence teams to run one joined hunt. Repository changes, editor execution and blockchain resolution can otherwise appear as unrelated low-confidence events. Extend software-trust controls beyond package signatures.
That’s Security.io Daily Headlines for Monday, September 21, 2026. Full reporting, sources, executive actions and today’s comic are available in the complete edition at Security.io. I’m Max Vogal. Thanks for listening.