Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Mobile Vikings

Bug bounty on Intigriti mobilevikings.be

Accepting reports Full safe harbor
Go to program
Top reward
€5,000
Top severity paid
Critical
Assets in scope
18
Public CVEs
1
Last change

At a glance

What to know before you start testing.

Pays up to €5,000
for critical bugs.
Report on Intigriti
Submit through the program page.
Full safe harbor
Good-faith research is authorised; no legal action.
No public write-ups
Keep findings private.

Rewards

What Intigriti lists as the payout for each severity.

Severity Reward
Critical €5,000 from €50
High €2,000 from €50
Medium €1,200 from €50
Low €150 from €75

Scope

18 assets you may test.

Web 10

  • api.unleashed.be
  • forms.mobilevikings.be
  • jimmobile.be
  • mgm.mobilevikings.be
  • mobilevikings.be
  • uwa.mobilevikings.be
  • vikingco.be
  • vikingdeals.be
  • vikinglab.be
  • vpn.mobilevikings.be

Wildcard domains 8

  • *.acc.mobilevikings.be
  • *.acc-pub.mobilevikings.be
  • *.dev.mobilevikings.be
  • *.dev-pub.mobilevikings.be
  • *.mas.mobilevikings.be
  • *.mobilevikings.be
  • *.prd.mobilevikings.be
  • *.prd-pub.mobilevikings.be

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Mobile Vikings (via Intigriti)'s policy.

While testing

  • Respect the scope of the program
  • Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)
  • Please do not use automatic scanners - be creative and do it yourself!
  • If you really need to use such a tool, limit your requests to 1 per second.

Not accepted

  • Outdated libraries with known vulnerabilities without an attack vector
  • Access token stored in local storage
  • Wordpress plugin confusion (plugins are updated manually by updating the source url)
  • Third party cookie manipulation trough request parameters and potential DoS attack vectors related to these cookies
  • Publicly exposed MSISDN's without other personaly identifieable information.
  • 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

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 9 minutes ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Before we tracked it

Scope and reward changes recorded before this page started tracking it.

  1. Scope removed

    uwa.mobilevikings.be

  2. Scope removed

    mobilevikings.be

  3. Scope removed

    vikingco.be

  4. Scope removed

    mgm.mobilevikings.be

  5. Scope removed

    forms.mobilevikings.be

  6. Scope removed

    jimmobile.be

  7. Scope removed

    api.unleashed.be

  8. Scope removed

    vpn.mobilevikings.be

  9. Scope removed

    vikinglab.be

  10. Scope removed

    vikingdeals.be

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD
CVESeverityPublished
CVE-2017-20182 Low 3.5 10 Mar 2023

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

True Vikings never entered the battlefield without their helmets. And we believe a secure environment, just like free access to open communication, is a worldwide human right. But even the best Viking Drakkars may sometimes encounter vulnerabilities. Brave sailors who discover leaks should be honored - not executed. Together with you and our broad community, we want to create a secure and safe environment for everyone.

Rules of engagement

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)

In scope

We're interested in all kinds of bugs that could affect user data or Mobile Vikings' integrity. These include - but are not limited to the following bugs:

  • Remote Code Execution
  • SQL Injection
  • File Inclusion / Directory Traversal
  • Cross Site Scripting
  • Cross Site Request Forgery with a realistic attack scenario
  • Privilege escalation
  • Significant enumeration attacks

Please do not use automatic scanners - be creative and do it yourself! Scanners 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 😉). If you really need to use such a tool, limit your requests to 1 per second.

Out of scope

Highlighted

Functionality

  • The live support chat

Known Issues

  • Outdated libraries with known vulnerabilities without an attack vector
  • Access token stored in local storage
  • Wordpress plugin confusion (plugins are updated manually by updating the source url)
  • Third party cookie manipulation trough request parameters and potential DoS attack vectors related to these cookies
  • Publicly exposed MSISDN's without other personaly identifieable information.

Domains

  • Any domain that is not listed in the Domains section, is out of scope for this program

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 attacks or brute force attacks
  • 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
  • Direct access to origin and bypassing CDN.

Severity

This program follows Intigriti's triage standards

FAQ

Can we receive test accounts?

Mobile Vikings

You can register an account here with your @intigriti.me address (don't forget this!):

Jim Mobile

You can register an account her with your @intigriti.me address (don't forget this!): https://jimmobile.be/en/e-services/#!/registration/

You don't need a Belgian sim card number to create a Jim Mobile account. You can fill in a dummy address and cancel on the payment step, at that point you have login credentials. Since it's a client side website you can at that point also make all calls. Some will fail because you don't have an active sim. If you need an active sim, contact us before hand, fill in our HQ address so we can forward the letter to whatever place you want/need. The HQ address is in the footer of the site.