Menu

Individual skill

network-replay

0upvotes

PCAP-based network replay attacks: capture auth sequences, session tokens, and protocol frames, then replay or inject to achieve unauthorized access or session hijack.

packages/decepticon/decepticon/skills/standard/post-exploit/network-replay/SKILL.md

Read pinned source

Source commit df879550544d36b6b1e69062f05adae28537adf2

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
6,573
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Network Replay Attack Playbook

> Authorized use only. Replay attacks require network capture of live traffic
> which may incidentally capture credentials or PII from non-target systems.
> RoE must explicitly authorize packet capture on the target subnet and name
> which protocols and systems are in scope.

## Overview

A replay attack reuses previously captured, valid network messages to
re-authenticate or re-authorize without knowing the underlying secret.
CAI's dedicated replay-attack agent covers this as a distinct offensive
primitive. Decepticon routes it here from any engagement where valid
traffic has been captured and the auth token / session state is reusable.
Back to top