Hunt for bugs and vulnerabilities in my projects
Rules for all my projects, current and future: what you may test and how to report a find. First reply within 7 days.
What you may test
Test only on your own accounts and your own devices. A new project falls under these rules as soon as it appears in the list.
- Chat Arenaworkingopen online
A game bot for your own chats and DMs, a mini app and a website.
- 23:59: City Without Dawnbetacan be downloaded
A test APK build from the game page: the game itself, saves, the APK build. Ads in the test build are test ads.
- Steady Volumeworkingcan be downloaded
A Firefox store extension and its code.
- Delaworkingopen online
A sync server on your own account, a web version, apps from the releases and the code. You can try to break the task encryption on your own data.
- Gridlore: Blocks and Runesbetacan be downloaded
A test APK build from the game page.
- Kolobok: Rolled Away!in developmentdemo only
There is no build to test yet. The game page has a video and screenshots, the tasks will appear when the game comes out.
- olerast.comworkingopen online
The whole site: pages, tools, the flasher, the schematic builder, search and this form.
- artel.redworkingopen online
The artel.red website.
- PAIKAin developmentopen online
The paika.ink website.
- Troll Botprototypeclosed source
The code is closed and the robot is not built yet. There is nothing to test for now, I will show the build in upcoming videos.
- ESP32 music playerprototypeopen source
The open libraries of the player. The player itself exists only in my code for now.
- Suflyorworkingcan be downloaded
An app from the GitHub releases and its code.
- Editing systemworkingclosed source
It works only on my machine and the code is not published. You cannot test the program, you can only watch a video it edited.
- Emotion keychainprototypeopen online
A browser simulator, the ESP32 test stand firmware and browser flashing, the engine and firmware code, the rev B board and case files.
- otisk: a pocket fingerprintprototypeclosed source
The code and the board files are closed and the keychain is not built yet. There is nothing to test for now, I will show the first sample in videos.
- olerast PULSEin developmentclosed source
The code is closed and the gadget is not built yet: there is research and an initial firmware skeleton. There is nothing to test for now.
- Haptic Gatewayprototypeclosed source
The code is closed, the bracelet is not built yet and the program has not connected to printers. There is nothing to test for now.
- A drone for the workshopin developmentclosed source
The project has only started: the hardware is not chosen, there is no code or drawings yet. There is nothing to test.
- Chipnikbetaopen online
The chipnik.dev website.
- Zamokbetacan be downloaded
A program from the GitHub releases and its code. You can test the encryption on your own test folders.
- No Fingerprintsworkingopen online
A browser page and its code.
- DITHR//CAMprototypeopen source
The firmware and its code. You can check the effects in the screen simulator from the repository.
How to test
- Test the addresses and apps from the list on your own accounts and your own devices.
- If you find a vulnerability, report it right away through the form below and do not dig further than you need to show it.
- Keep the details of a find to yourself until the report status becomes Fixed. After that you may talk about it in a video or a post.
Severity scale
- critical
- Access to someone else's data or someone else's account without a password.
- high
- Harm to another person once a condition is met, for example code that runs for another visitor, or a swapped download file.
- medium
- Weakened protection without direct harm: service paths and versions are visible, a page is open that should not be.
- low
- A bug with no harm to other people's data: a game crash, a dead button, a layout that broke on a phone.
Send typos and ideas the same way, they do not need a severity.
Response times
- First reply
- 7 days
- Fix for critical
- within 7 days
- Fix for high
- within 30 days
- Medium and low
- in upcoming updates
I run the projects alone, so fix times are a guideline. The status and my reply are visible at the report link.
Safe harbor
If you tested by these rules and reported to me through the form, I will not file complaints or reports against you and will not ask you to delete the find. If you accidentally saw too much, stop and say so in the report: a careless mistake will not be grounds for a claim.
Rewards
I do not pay money for finds. I will show the best finds in the next video on the olerast channel and add them to the hall of fame below under the nickname from the report. I decide who to show.
Hall of fame
Empty for now. Be the first.
Report a bug
A report is visible only to me. After sending you get a report code and a secret link: it shows the status, my reply and a place to add details.