____  ____ ____     ____                  ____            ____  _
  / __ \/ __// __/    / __ \ ___   ___  ___ / __/ ___  ____ / __/ / /_ ___   ____ ___
 / /_/ /\ \ _\ \     / /_/ // _ \ / _ \(_-<_\ \  / -_)/ __/_\ \  / __// _ \ / __// -_)
 \____/___//___/     \____/ \___// .__/___/___/  \__/ \__//___/  \__/ \___//_/   \__/
                                /_/

# Start with Node.js
npx create-oss-store my-ctf-lab && cd my-ctf-lab && npm start

# Start with Docker
docker run -p 127.0.0.1:3000:3000 leogra/oss-oopssec-store

# Then open http://localhost:3000 and start hacking

Getting started

[!TIP] All captured? Join the Hall of Fame, star the repo, and post your route in Show your solve.

_{New to offensive security? The TryHackMe room wraps the first flags in a guided narrative.}

Table of contents

• Features
• Why OopsSec Store?
• Installation
  • Quick start (npm)
  • Docker
• Hall of fame
• Community
• Project structure
• Testing
• Disclaimer
• Contributing
• Educator Kit
• Project stats

[!WARNING] This application contains intentional security flaws and must never be deployed in a production environment.

Features

• Intentionally vulnerable e-commerce app (XSS, CSRF, IDOR, JWT attacks, path traversal, SQL injection, and more)
• Built with Next.js (App Router), React, TypeScript, Prisma, and SQLite
• REST API with documented attack vectors
• 36 CTF challenges across 11 chapters, laid out as a structured learning roadmap
• Vulnerability documentation and community walkthroughs for each challenge
• A guided TryHackMe room: The Summer Audit, 8 tasks and 7 flags, as a narrative on-ramp for newcomers
• Automated tests that verify exploits still work (PRs that accidentally fix a vuln will fail CI)

Why OopsSec Store?

Modern frameworks change where security vulnerabilities appear and how they should be fixed. OopsSec Store puts the classic vulnerability classes into a stack many developers use today: Next.js App Router, React, TypeScript and Prisma.

Server-rendered components, middleware and ORMs introduce different trust boundaries and failure modes. Several challenges also reproduce published CVEs against this stack.

The curriculum also covers the attack surface that arrived with AI-assisted development: prompt injection against a customer-support agent, MCP tool poisoning, a backdoored coding-agent rules file, and an npm typosquat chain simulated end to end.

_{Last verified June 2026, against Juice Shop v20 and DVWA 2.x. Spotted an inaccuracy? Open an issue or open a PR.}

Installation

Quick start

npx create-oss-store my-ctf-lab
cd my-ctf-lab
npm start

Then open http://localhost:3000 in your browser.

Manual setup

Clone the repo and run the setup script:

git clone https://github.com/kOaDT/oss-oopssec-store.git
cd oss-oopssec-store
npm run setup

This creates the .env file, installs dependencies, sets up the SQLite database, seeds it with CTF flags, and starts the app on port 3000.

Docker

No Node.js required. Just Docker.

127.0.0.1:3000:3000 keeps the lab reachable only from your own machine. Use plain -p 3000:3000 only on an isolated VM you control.

From Docker Hub (quickest)

docker run -p 127.0.0.1:3000:3000 leogra/oss-oopssec-store

To persist data across restarts:

docker run -p 127.0.0.1:3000:3000 -v oss-data:/app/data leogra/oss-oopssec-store

From source (Docker Compose)

git clone https://github.com/kOaDT/oss-oopssec-store.git
cd oss-oopssec-store
docker compose up -d      # Start in background (builds the image on first run)
docker compose logs -f    # Follow container logs
docker compose down       # Stop the container
docker compose down -v    # Stop and wipe data for a fresh start

With npm installed, the same four are npm run docker:up, docker:logs, docker:down and docker:reset.

The database initializes on first start. Data persists across restarts via Docker named volumes, including flag progress, users and uploads.

Hall of fame

Found all the flags? Open a pull request to join the Hall of Fame. Add your entry to hall-of-fame/data.json and your profile will show up on the /hall-of-fame page in the app.

Once your entry is merged, a badge is generated for you and served from the docs site:

[![OopsSec Store Hall of Fame](https://koadt.github.io/oss-oopssec-store/badges/%3Cyour-username%3E.svg)](https://github.com/kOaDT/oss-oopssec-store#hall-of-fame)

A 1200x630 social card lives at the same path with a .png extension.

[![OopsSec Store Hall of Fame](https://koadt.github.io/oss-oopssec-store/badges/%3Cyour-username%3E.png)](https://github.com/kOaDT/oss-oopssec-store#hall-of-fame)

Both are copy-paste ready from your card on the /hall-of-fame page, in Markdown, HTML or as a bare URL.

Questions, solutions and feedback live in Discussions.

Project structure

Testing

The project includes security regression tests that make sure all exploit chains and flags still work. These tests deliberately validate insecure behavior. They run on every PR, so if you accidentally patch a vulnerability, CI will catch it.

Running tests

# Unit tests (utility functions: MD5 hashing, JWT, input filters)
npm run test:unit

# API exploitation tests (requires a running server)
npm run test:api

# E2E exploitation tests (requires a running server)
npm run test:e2e

# Open Cypress interactive mode
npm run test:e2e:open

# All tests
npm run test:ci

Disclaimer

[!CAUTION] This project is for educational and authorized security testing only. It contains intentional vulnerabilities and insecure configurations. The authors are not responsible for any misuse, damage, or unauthorized access. Use it in isolated environments.

Contributing

OSS – OopsSec Store is MIT-licensed. Contributions are welcome.

Ways to contribute:

• Add new security challenges
• Write or improve walkthroughs
• Extend the application
• Report and fix bugs
• Improve documentation

Check the Roadmap for planned work, or grab a good first issue.

Found all the flags? Share your walkthroughs on the docs site.

For bugs or suggestions, open a GitHub Issue. See CONTRIBUTING.md for guidelines.

🎓 Using OopsSec Store in a course or CTF?

Check out the Educator Kit - a ready-to-use guide with OWASP coverage grids, syllabus templates, deployment FAQ, and a student report template. Building your own tooling around the curriculum? The whole thing is published as a machine-readable feed at challenges.json, regenerated on every docs deploy.

Project stats