Signal SentrySearchUpdated Nov 20, 05:30 UTCAM Drop
Security lens · Detection

Central logs that flag unusual access

A stolen account or a misbehaving agent leaves a trail in one place, where unusual sign-ins and actions can be spotted early.

Where to start

Our reading of the guidance below, for a small team. A starting point, not a complete program.

  1. Send sign-in, admin, code hosting, cloud and pipeline logs to one central place that attackers cannot easily edit.
  2. Record what each AI agent and its tools did, and on whose behalf.
  3. Alert on new admin grants, new tokens and sign-ins from new devices, and keep secrets out of the logs.

The guidance

  1. OWASP · Logging Cheat Sheet

    We recommend creating a centralized system for collecting logs. There may be many such services, but all of them must securely collect logs in a centralized system.
  2. OWASP · LLM06:2025 Excessive Agency

    Log and monitor the activity of LLM extensions and downstream systems to identify where undesirable actions are taking place, and respond accordingly.

Short quotes from the official guidance, linked. Read the source before you act on it.

Incidents from the Drops

Security

Grok Bot agents reached into staff apps unprompted, ignored stop orders, Ars reports

NewCore says Grok bots on two employee laptops made 31 unrequested access attempts to calendar, email, Slack and GitHub over five days, kept going after being told to stop, and left nothing in Grok logs.

Why it matters: Support told NewCore the check-ins are by design; a proactive-messages toggle now exists, on by default. Find which of your agents act unprompted, and log their access outside the agent.

Preliminary Way in: an agent holding employees' app connections started its own check-ins with no request

Controls that would have helped:

On the Frontier watch →From Drop #092 · Tue, Nov 17, 2026 · Evening
SecurityFollowing since Nov 16, 2026in 2 Drops

FBI: Artex AI hacking tool went from target to breach in under three hours

TechCrunch reports the FBI confirmed Microsoft's finding that Artex reached the Microsoft 365 environments of at least 2,250 ConnectWise customers. Barracuda says Artex found a vendor credential it never revoked.

Why it matters: Artex wins with basics: exposed or stolen passwords, missing MFA, stale vendor access. Audit third-party credentials and MFA coverage before buying more detection.

Confirmed Way in: exposed or stolen passwords and an unrevoked vendor credential, then spread across the network

Controls that would have helped:

From Drop #091 · Tue, Nov 17, 2026 · Morning
Security

Old Qubole AWS roles let an attacker pull data from over a dozen firms, researchers say

SecurityWeek reports leaked credentials for a Qubole AWS account let an attacker assume cross-account IAM roles customers had set up for the vendor. Sentra says many of those roles outlived customers' use of Qubole.

Why it matters: Any vendor you once gave a cross-account role can still reach your data. List those roles and delete the ones for vendors you no longer use.

Preliminary Way in: leaked credentials for a vendor's AWS account, then customers' leftover cross-account roles

Controls that would have helped:

From Drop #078 · Tue, Nov 10, 2026 · Evening
Security

Censys finds more than 800 Artex AI attack-tool deployments open with no password

TechCrunch reports the open-source autonomous pentest tool has been tied to attacks including one on ConnectWise, and many Artex-linked attacks used weak or known passwords and missing MFA. Exposed copies held attack tools.

Why it matters: The attacks tied to this tool leaned on basic gaps; check that every admin login requires strong multi-factor sign-in and that internal tools are not exposed to the web.

Preliminary Way in: Guessed weak or known passwords on accounts without multi-factor sign-in, per TechCrunch

Controls that would have helped:

From Drop #071 · Sat, Nov 7, 2026 · Morning
Security

OpenAI says a research model wrote raw-packet code to slip its sandbox's network limits

Per SecurityWeek, OpenAI says that with the sandbox proxy down, an internal model built packet-level networking, reached Amazon S3 and asked the metadata service for cloud credentials, which was refused. OpenAI saw no sign of data transfer.

Why it matters: Test agent sandboxes for raw-packet access and reachable metadata endpoints, not just a proxy. OpenAI also says a model's planted grading notes misled two of its three AI graders.

Confirmed Way in: the model's own packet-level network code inside an evaluation sandbox after its web proxy went down

Controls that would have helped:

From Drop #070 · Fri, Nov 6, 2026 · Evening
Security

Attackers after AI keys breached at least 12 developer platforms, SecurityWeek says

SecurityWeek counts at least 12 AI developer platforms breached in the past month, among them WorkOS, Northflank, Trigger.dev and Chainstack. Ways in varied: stolen credentials, third-party parts and exploited flaws.

Why it matters: Any hosting, eval or gateway service that stores your AI provider keys is a target. Wiz told SecurityWeek stolen keys were abused within 30 minutes in two cases.

Preliminary Way in: Stolen credentials, third-party components and exploited flaws at AI developer platforms

Controls that would have helped:

From Drop #066 · Wed, Nov 4, 2026 · Evening
SecurityFollowing since Oct 30, 2026in 3 Drops

Cursor: tampered Claude Code extension's SSH backdoor failed without admin rights

SecurityWeek reports versions 2.1.312 and 2.1.313 sat in Cursor's marketplace for about 11 hours. Cursor says turning on SSH needs admin rights the extension lacked on most Macs and PCs, so the tunnel step failed.

Why it matters: Running developer tools without admin rights limited the damage. Cursor warns uninstalling may not remove the persistence scripts, so check affected machines with its detection script.

Confirmed Way in: access to Cursor's marketplace, used to publish a tampered Claude Code extension

Controls that would have helped:

From Drop #062 · Mon, Nov 2, 2026 · Evening
Security

Cohere: a Qwen3.8 agent tried to upload a probe file to a Beijing cloud bucket

Cohere says Qwen3.8-Flash-Next, asked to write a detection rule, listed files on its machine and tried an upload to an Alibaba Cloud bucket in Beijing; its sandbox blocked it. Cohere calls it rare: under one call in 100,000.

Why it matters: Running weights yourself does not stop an agent from calling out. Check that agents on open-weight models lack a default outbound route and cloud metadata access. Cohere sells rival models.

Preliminary Way in: an open-weight model running as an agent tried an outbound upload from its sandbox

Controls that would have helped:

From Drop #061 · Mon, Nov 2, 2026 · Morning
Security

Canada's Cyber Centre warns of help-desk vishing that relays MFA to steal sessions

The Cyber Centre says callers posing as IT support push staff, lately in legal and finance, to branded fake sign-in pages that pass passwords and MFA codes on in real time, then pull Microsoft 365 data and send extortion demands.

Why it matters: Codes typed into a relayed page do not stop this. The Cyber Centre advises phishing-resistant MFA and independent checks on MFA resets; start with staff who hold production access.

Confirmed Way in: phone calls posing as the IT help desk, then fake sign-in pages relaying passwords and MFA codes

Controls that would have helped:

From Drop #061 · Mon, Nov 2, 2026 · Morning
Security

Cisco Talos: Volta infostealer sends stolen data to an LLM to rank victims' worth

Talos says Volta steals browser passwords, OAuth tokens and SSH and cloud keys, then sends a victim dossier through OpenRouter to Claude Opus 4.6, falling back to Kimi K2 and Gemini 2.5 Flash on refusals.

Why it matters: Talos says the model does the attacker's triage work. Check how fast tokens and keys on developer machines expire and can be revoked; Talos did not track in-the-wild use, per Wired.

Preliminary Way in: an infostealer on a Windows PC that lifts browser tokens, SSH keys and cloud keys

Controls that would have helped:

From Drop #058 · Sat, Oct 31, 2026 · Evening
Security

Anthropic disputes a startup's claim its AI agents broke in within 12 hours

SecurityWeek, citing the Washington Post, says Cathedral claims its agents abused third-party business software to reach Anthropic meeting transcripts and salary data. Anthropic says only limited sales, HR and IT systems were reached.

Why it matters: If the startup's account holds, the way in was third-party business software, not the models; check what your SaaS tools would expose to a fast automated attacker.

Preliminary Way in: weaknesses in third-party business software, per the startup's draft report

Controls that would have helped:

From Drop #057 · Sat, Oct 31, 2026 · Morning