urgentstill live
Unknown credential is active from an unresolved endpoint.
A live coding session changed the trust picture because identity, host, and credential context all weakened at once.
Why security cares
This is the fastest path from uncertainty to company risk because the session is still active and the credential may be shared beyond one developer machine.
Affected scope
Potential reach includes auth-service files, customer-facing service lanes, one shared AI credential lane, and any downstream systems the key can call.
Why confidence is not higher
The key is clearly new and the session is live, but host ownership is still unresolved so attribution is incomplete.
sk-ant-...C00110.0.1.44active session · 22mclaude-sonnet-4-6
Blast radius: credential + host + live session + auth context
Suspend or verify the key first, then bind 10.0.1.44 to an owner before the session widens scope.
Contain key + inspect session
warningreview now
Sensitive file access is now paired with a plain HTTP destination.
The issue is the relationship, not the individual events. Access to auth.ts matters more once it is followed by an unusual outbound edge.
Why security cares
Sensitive file access becomes materially more important when it is adjacent to unencrypted network activity that could move secrets or code context outside expected lanes.
Affected scope
Touches auth-service code, one active session, and a destination not yet labeled as expected internal traffic.
Why this is credible
The file access and outbound call happened in the same session window. The blind spot is destination intent, not whether the relationship occurred.
/src/auth.ts10.0.2.15:8080httpsame session window
Blast radius: file + session + destination + possible secret context
Inspect the secondary call, classify the destination, and confirm whether any sensitive content could have crossed the boundary.
Inspect destination + file trail
stablemonitor only
Most activity remains inside a known-good operating lane.
The page should say this clearly so security can focus on the exceptions without feeling like the whole environment is on fire.
Why security cares
Reassurance is operationally useful. It reduces alert fatigue and makes the truly unusual stories feel proportionate instead of ambient.
Affected scope
Most developer and CI activity stays within expected hosts, approved credentials, encrypted traffic, and standard model routing.
Why confidence is high
Known user, known endpoint, expected model, and expected credential combinations still dominate the environment.
34 known-good sessionsexpected keysexpected hostsnormal model mix
Blast radius: low concern baseline
Keep this compressed and continue monitoring; do not let normal volume drown the urgent lane.
Monitor only