> For clean Markdown of this page, append .md to its URL. For the complete documentation index, see https://www.superagent.sh/llms.txt.


Adversarially test installable software in an isolated sandbox from your installation instructions.

# Packages

Package Red Team runs perform automated black-box adversarial testing against installable software. You supply installation instructions; Superagent provisions an isolated sandbox, follows those instructions, discovers the local attack surface, and tries to breach the installed package.

### Start a package run

1. Open **Red team** and select **New report**, or go to `/app/reports/new`.
2. Choose **Package**.
3. Enter **Installation instructions** (required): how to install and, if needed, start the package.
4. Optionally add a **Specific prompt** to steer the campaign.
5. Submit to provision the isolated runner and open the live detail page.

Examples of installation instructions:

```text
brew install foo
```

```text
npm i -g bar@1.2.3
bar --serve --port 8080
```

```text
pip install baz==1.0.0
baz serve --host 127.0.0.1
```

Package reports created in the dashboard are labeled **Manual** in the report list. Reports created through REST or MCP are labeled **API**.

### What the runner does

In the sandbox, Superagent:

1. Follows your installation instructions
2. Discovers local surfaces such as CLIs, local ports, config files, and privilege boundaries
3. Runs adaptive attacks against those surfaces
4. Emits findings with reproduction steps and evidence

The install instructions and any specific prompt are treated as untrusted input and execute only inside the isolated sandbox. Organization secrets are not injected.

### REST API and MCP

Programmatic clients can start Package runs with:

- `POST /api/v1/reports/package`
- MCP tool `create_package_report`

Both accept `installation_instructions` (required) and `custom_goal_prompt` (optional). See the [Reports API](https://www.superagent.sh/docs/api/reports) for request fields and examples.

### The package detail page

Each Package report lives at `/app/reports/package/[id]`. From there you can:

- Follow expandable runner logs
- Review findings and risk counts
- Inspect installation instructions, optional prompt, cost, and runtime status
- Delete or rerun the report

Findings also appear in the shared [Findings](https://www.superagent.sh/docs/concepts/findings-and-reports) queue.

## Next steps

- [Review findings and reports](https://www.superagent.sh/docs/concepts/findings-and-reports)
- [Understand supply chain scanning](https://www.superagent.sh/docs/security-workers/pr-security/supply-chain-scanning)
- [Scan packages before installation](https://www.superagent.sh/docs/security-workers/agent-guardrails/extensions-and-packages)

---
Source: https://www.superagent.sh/docs/security-workers/red-team/packages
Index: https://www.superagent.sh/llms.txt