By participating in this program, you agree to:

• Respect the Community Code of Conduct
• Respect the Intigriti Terms and Conditions
• Respect the scope of the program
• Not discuss or disclose vulnerability information without prior written consent (including PoC’s on YouTube and Vimeo)

We are looking for security vulnerabilities and for vulnerabilities that could lead to databreaches. In order to get the maximum value out of your creativity, we are opening the scope to our complete web environment.

We are especially looking for vulnerabilities regarding

• Data extraction
• Horizontal or vertical privilege escalation
• Influencing game payouts
• Adding money to your account without or with wrongfull payments
• ...

In our opinion, the most interesting areas to focus would be:

• api.napoleongames.be (Mobile API)
• Voucher payments
• Gameserver entry point

Do not test againt our 3rd party game / sports / live casino providers:
Attention: this list may not be up-to-date.

• Kambi (*.kambi.com)
• Evolution (*.evolution.com)
• Netent (*.netent.com)
• Quickfire (*.quickfiregames.co.uk)
• Magnet Gaming (*.magnetgaming.com)
• Netent (*.casinomodule.com)
• MicroGaming (*.gameassists.co.uk)
• Evonetworks (*.evonetworks.net)

Do not test on our test environments:

• *test *

IMPORTANT, known issues:

• CSRF
• Open Redirect

Napoleongames Applications:

• adserving.napoleongames.be
• hecate.napoleongames.be
• affiliates.napoleongames.be and domains with DNS to the same location (eg. affiliateadmin.napoleongames.be)

Trying to influence our payment system is allowed (and even highly appreciated as a report!), but do not test againt our 3rd party payment providers.

• Neteller
• HiPay
• Skrill
• Paysafe

Application

• Pre-auth account takeover / oauth squatting
• Self-XSS that cannot be used to exploit other users 
• Verbose messages/files/directory listings without disclosing any sensitive information
• CORS misconfiguration on non-sensitive endpoints
• Missing cookie flags
• Missing security headers
• Cross-site Request Forgery with no or low impact
• Presence of autocomplete attribute on web forms
• Reverse tabnabbing
• Bypassing rate-limits or the non-existence of rate-limits.
• Best practices violations (password complexity, expiration, re-use, etc.)
• Clickjacking on pages with no sensitive actions
• CSV Injection
• Host header injection without proven business impact
• Blind SSRF without proven business impact (DNS pingback only is not sufficient)
• Disclosed and/or misconfigured Google API key (including maps)
• Sessions not being invalidated (logout, enabling 2FA, password reset, ...)
• Hyperlink injection/takeovers
• Mixed content type issues
• Cross-domain referer leakage
• Anything related to email spoofing, SPF, DMARC or DKIM
• Content injection
• Username / email enumeration
• E-mail bombing
• HTTP Request smuggling without any proven impact
• Homograph attacks
• XMLRPC enabled
• Banner grabbing / Version disclosure
• Open ports without an accompanying proof-of-concept demonstrating vulnerability
• Weak SSL configurations and SSL/TLS scan reports
• Not stripping metadata of images
• Disclosing credentials without proven impact
• Disclosing API keys without proven impact
• Same-site scripting
• Subdomain takeover without taken over the subdomain
• Arbitrary file upload without proof of the existence of the uploaded file

General

• In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate.
• Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited, may be excluded or be lowered in severity
• Spam, social engineering and physical intrusion
• DoS/DDoS attacks or brute force attacks.
• Vulnerabilities that are limited to non-current browsers (older than 3 versions) will not be accepted
• Attacks requiring physical access to a victim’s computer/device, man in the middle or compromised user accounts
• Reports that state that software is out of date/vulnerable without a proof-of-concept

Severity assessment:

This program follows Intigriti’s contextual CVSS standard
Note that Napoleon Games will perform risk assesment for each individual issue.

Cool-down period for zero-days
Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty. We may however decide to offer a bonus at our own discretion!

Examples of potential critical business impact:

• SQL injection
• Vertical privilege escalation
• Bugs in our games that allow you to:
  • Extract game-related info of other players
  • Predict your chances of winning
  • Influence to win a game

Examples of potential exceptional business impact:

• Remote code execution

Can we get test accounts

You are free to register an account but please use your @intigriti.me address so we can track researchers in our production environment. Researchers that don't use an @intigriti.me address will not be rewarded a bounty.

In case you are not able to register or you want to work with credits to test games, you can contact NapoleonGames through the Intigriti portal to request this. At that point you will be flagged as a test account and you will receive test money. Please note that by doing this, certain features (withdrawel,...) will no longer work on your account.

Cash player

If you do a self-registration you can enable cash modus and you will receive some credits for free.

How to register

Bypassing National number verification
Go to https://en-gb.napoleongames.be and click on 'Register now'.
--You will now be forwarded to the registration page, which is only available in Dutch anymore--
First page: Registratie/Account gegevens
Fill in your @intigriti.me mail address and type in your password in the 'Wachtwoord' field.
Check all boxes, and click on 'Registeren'.
Second page: Choose 'Voltooi uw account handmatig'.
Third page: Registratie/Persoonlijke gegevens
Fill in all fields.
'Voornaam' = first name
'Achternaam' = last name
'Geboortedatum' = Date of birth
'Geboorteplaats' = Place of birth
Choose 'FR' in the 'Document van' field and enter a passport/ID-cardnumber in the 'Nationale identiteitskaart nr.*' field (12 numbers).
Choose 'België' in the 'Land van verblijf' field (important because otherwise it's possible that you can't use your account due to geoblocking).
Fill in all other mandatory fields.
'Straat' = street
'Number/bus' = streetnumber
'Stad' = City
'Postcode' = Postal Code
'Telefoonnummer' = telephone number
Click on 'Registreren'.