CookieFarm
Exploits

Running Exploits

Run exploits with `ckc exploit test/run`, including tick/thread tuning and submit mode.

Running Exploits

Test mode (always first)

ckc exploit test -e my_exploit -n CookieService -t 30 -W 5

test enables Python runtime -x mode: execution only on NOP team.

exploit test

Run mode (competition)

ckc exploit run -e my_exploit -n CookieService -t 60 -W 20

exploit run

Main flags

  • -e, --exploit: exploit path or name
  • -n, --name: service name
  • -t, --tick: seconds between rounds
  • -W, --workers_number: target concurrency
  • -P, --process_mode: using multiprocessing instead of multithreading
  • -d, --detach: start in background
  • -S, --submit: direct HTTP submit instead of CKP

Practical tuning

  • Competition start baseline: -t 60, -W 10..20
  • Unstable services: lower -W
  • Saturated checker: increase -t
  • Many failed without error: verify regex/shared config alignment

If the user needs to run an exploit that uses Sagemath (or other no-thread-safe libraries), use --process_mode to run in multiprocessing mode.

In particular, it's suggested to use Sagemath installed via binary or by conda instead of the installation via pip or uv pip. To use local Sagemath and CookieFarm, both must be in the same environment.

Stop and list

ckc exploit list      # local exploit templates
ckc exploit listrun   # running exploits with PID
ckc exploit stop -p <pid>

Manual single-flag submit

ckc exploit submit -f 'FLAG{...}' -n CookieService -t 7 -m 'manual retry'

How is this guide?

Creating Exploits

How to create Python exploits compatible with CookieFarm.

Exploiter Library

Internals of the Python `cookiefarm` runtime used by exploits.

On this page

Running ExploitsTest mode (always first)Run mode (competition)Main flagsPractical tuningStop and listManual single-flag submit