A pokemon-like project game where you level up by hacking your neighbor
CTF BourgPalette
A pokemon-like project game where you level up by hacking your neighbor.
You play as a new hacker. You are not trying to capture all the pokemons but to capture all the flags! CTF is for Capture the Flag, a famous term in cybersecurity where you can try to figure out how to infiltrate and exploit on a simulation ecosystem. It’s the same in CTFBourgPalette.
Built during the Secureworks Cybersecurity Literacy Challenge 2022.
Usage
Dependencies
Before running CTF BourgPalette the following dependencies need to be installed.
| Dependencies | Version |
|---|---|
| npm | 8+ |
Installation and launch
$ git clone https://github.com/VBoureaud/CTFBourgPalette.git
$ cd CTFBourgPalette
$ npm install
$ npm start
Demo
There is a live demo running on vercel. You can find it here
Update the maps
To update the maps you will need a software named Tiled. Open a map file map.tmx, and locate your tilesets assets/tilesets.png. Then you can edit your map but be careful, respect the layers. When you are done save your map.tmx and export as a map.json.
In the Future
Still a lot of ideas that I would like to implement:
| Ideas |
|---|
| Quests about Phising, Sim Swap, Multi-Auth, OSINT, Rogue Access Point, Cryptographic |
| P5.js game to simulate Bruteforce Attack |
| Click on flag to auto copy |
Known issues
To be corrected in the next version.
| Issues |
|---|
| Some events are launched asynchronously with PhaserJS and can cause a pause movement for the player who needs to reload the page. |
Find an issue ? Contact me at valentin@boureaud.com
Credits
Some awesome libraries/projects help power this one:
- PhaserJS, for the game engine
- Create-React-Phaser3-App, for the boilerplate ReactJS + PhaserJS
- Ariel Roffe, for the structure of the phaserJS game
- NES.css for the crazy NES design
- Ant Design for the reactJs design part
- TypeScript, write JS with syntax for types
- Reactjs – Library for building user interfaces
Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change. Please make sure to update tests as appropriate.