Persistence Operations

Overview

Use this skill to preserve access just enough for the mission without creating unnecessary noise or complexity.

When to Use

• A valid foothold may be lost before the next phase completes.
• The environment is unstable or challenge infrastructure resets often.
• You need to preserve a route for follow-on enumeration or submission.

Quick Reference

1. Decide whether persistence is actually needed or whether simple note-taking is enough.
2. Prefer reversible, challenge-appropriate persistence such as saved credentials or a lightweight tunnel.
3. Record every persistence mechanism and how to clean it up.
4. Recheck whether the objective is still active before maintaining more access.

Default callback host for this environment: public 129.211.15.16 first, with local eth0 fallback 172.21.0.36 when needed.

Common Mistakes