---
title: "Hijacked-agent alerts · Ataris"
description: "A legitimate customer's agent suddenly reads secrets, then exfiltrates, scans, or mines. Ataris raises an alert you can pass to that customer, or sell to them as a premium security tier."
canonical: "https://ataris.dev/product/hijacked-agent-alerts"
last-updated: 2026-11-02
---
# Tell customers when their agent turns.

A legitimate customer's agent suddenly reads secrets, then exfiltrates, scans, or mines. Ataris raises an alert you can pass to that customer, or sell to them as a premium security tier.

## Good customers get hijacked too.

Agents read untrusted input all day. One poisoned page or package can turn a paying customer's agent into something that steals their keys or mines on your hardware. The account is real. The behavior isn't.

### 1. Know: Know each customer's normal.

A real customer's sandboxes have a shape: the destinations they reach, how much they upload, how hard they run the CPU. Ataris sees that shape from the host.

Example (acme · usual): destinations = github.com, pypi.org, api; uploads = small, to own API; CPU = bursty builds.

### 2. Catch: Catch the turn.

New destinations, an upload spike, a scan, or a miner where there was none. Ataris flags the change on that customer, so a trusted account doesn't get a pass.

Example (acme · vm-c21e): new destination = 198.51.100.23:443; upload = 38 MB, first ever; then = SYN sweep tcp/6379.

### 3. Route: Send it to the customer.

The alert goes to your webhooks with the host, the sandbox, the timeline, and the evidence. Forward it to the customer, or package it as a security tier they pay for.

Example (webhook · alert): customer = acme; evidence = timeline + flows; delivered to = your webhook.

## From detection to customer alert.

Everything a provider needs to turn a host-side detection into something a customer can act on.

- **Signals.** Changes from the customer's usual behavior. new outbound destinations, upload spikes, scanning, mining.
- **The alert.** What travels with it. host and sandbox, timeline of the change, flow evidence, memory snapshot, on request.
- **Your options.** How providers use it. forward to the customer, premium security tier, your own SOC, API and webhooks.

## Related

- [Hijacked agents](https://ataris.dev/use-cases/hijacked-agents.md): A paying customer's agent turns
- [AI agent sandboxes](https://ataris.dev/use-cases/agent-sandboxes.md): Firecracker, gVisor, Kata, containers
- [Guest memory inspection](https://ataris.dev/product/memory-inspection.md): Processes and binaries from a flagged VM

## Give your customers a security tier.

Book a demo and we'll show how hijacked-agent alerts reach your customers.

[Book a demo](https://ataris.dev/contact)