- Top reward
- €1,500
- Top severity paid
- Critical
- Assets in scope
- 20
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to €1,500
- for critical bugs.
- Report on Intigriti
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
Rewards
What Intigriti lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
€1,500 from €1,000 |
| High |
|
€250 |
| Medium |
|
€100 |
Scope
20 assets you may test.
Web 12
- career.bpost.be
- dmm.bpost.be
- eshop.bpost.be
- imove.bpost.cloud
- maxiresponse.bpost.be
- my.bpost.be
- procuration.bpost.be
- quickstamp-gb.bpost.be
- register.bpost.be
- validationlist.bpost.be
- www.bpost2.be
- www.bpost.be
Wildcard domains 5
- *.acbpost.be
- *.bpost.be
- *.bpost.cloud
- *.landmarkglobal-group.com
- *.stbpost.be
Android apps 2
- be.bpost.mobilecard
- be.bpost.mybpost
Hardware and IoT 1
- bpost Parcel Lockers
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Bpost (via Intigriti)'s policy. "We" in these lines means the program, not this site.
While testing
-
It’s forbidden to use automatic scanners - be creative and do it yourself!
-
We cannot accept any submissions found by using automatic scanners.
-
Do NOT discuss bugs.
-
You can send us a video as proof of concept, but remember to change its privacy settings to private
-
Provide detailed but to-the point reproduction steps
-
Include a clear attack scenario. How will this affect us exactly?
-
Remember: quality over quantity!
Not accepted
-
API key disclosure without proven business impact
-
Wordpress usernames disclosure
-
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 without proven impact/unrealistic user interaction
-
CSV Injection
-
Sessions not being invalidated (logout, enabling 2FA, etc.)
-
Tokens leaked to third parties
-
Anything related to email spoofing, SPF, DMARC or DKIM
-
Content injection without being able to modify the HTML
-
Username/email enumeration
-
Email bombing
-
HTTP Request smuggling without any proven impact
-
Homograph attacks
-
XMLRPC enabled
-
Banner grabbing/Version disclosure
Summarised with AI from the program policy on Intigriti, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 15 minutes ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.
Original policy
Copied from www.intigriti.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Description
The purpose of this website is to publish general information about bpost and its subsidiaries and their respective activities.
Rules of engagement
Cloud services
- For that part of our services that are hosted on the cloud , there's a limitiation on which cloud services you can test without additional approval. Check the respective services and reassure you're not violation their policies. eg Amazon: The most up to date info is available on https://aws.amazon.com/security/penetration-testing/
Guidelines
- It’s forbidden to use automatic scanners - be creative and do it yourself! We cannot accept any submissions found by using automatic scanners. Scanners also won't improve your skills, and can cause a high server load (we'd like to put our time in thanking researchers rather than blocking their IP's :-))
- Do NOT discuss bugs. You can send us a video as proof of concept, but remember to change its privacy settings to private
Reporting Guidelines
- Provide detailed but to-the point reproduction steps
- Include a clear attack scenario. How will this affect us exactly?
- Remember: quality over quantity!
In scope
We're interested to hear about any issue that potentially compromises our company or its user's security. Before submitting a vulnerability, make sure to check that it's not listed in our out of scope policy (which you can find below). If you have additional questions about our program feel free to contact us through intigriti's support by using the button on the right-hand side (Ask scope question).
Out of scope
Application
- API key disclosure without proven business impact
- Wordpress usernames disclosure
- 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 without proven impact/unrealistic user interaction
- CSV Injection
- Sessions not being invalidated (logout, enabling 2FA, etc.)
- Tokens leaked to third parties
- Anything related to email spoofing, SPF, DMARC or DKIM
- Content injection without being able to modify the HTML
- Username/email enumeration
- Email bombing
- HTTP Request smuggling without any proven impact
- Homograph attacks
- XMLRPC enabled
- Banner grabbing/Version disclosure
- Not stripping metadata of files
- Same-site scripting
- Subdomain takeover without taking over the subdomain
- Arbitrary file upload without proof of the existence of the uploaded file
- Blind SSRF without proven business impact (pingbacks are not sufficient)
- Disclosed/misconfigured Google Maps API keys
- Host header injection without proven business impact
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
- Spam, social engineering and physical intrusion
- DoS/DDoS and CPDoS attacks or brute force attacks or enumerating ( >1000 )
- Vulnerabilities that only work on software that no longer receive security updates
- Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
- 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
- Reports that state that software is out of date/vulnerable without a proof-of-concept
Mobile
- Shared links leaked through the system clipboard
- Any URIs leaked because a malicious app has permission to view URIs opened
- The absence of certificate pinning
- Sensitive data in URLs/request bodies when protected by TLS
- Lack of obfuscation
- Path disclosure in the binary
- Lack of jailbreak & root detection
- Crashes due to malformed URL Schemes
- Lack of binary protection (anti-debugging) controls, mobile SSL pinning
- Snapshot/Pasteboard leakage
- Runtime hacking exploits (exploits only possible in a jailbroken environment)
- API key leakage used for insensitive activities/actions
Severity
Currently we don't give a reward. You could be elected though for a bonus.