Tapfiliate B.V.
Bug bounty on security.txt tapfiliate.com
- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 1
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays cash
- Amounts are not published; ask before you invest time.
- Report by email
- [email protected]
- No public write-ups
- Keep findings private.
Rewards
What the company's own policy page says it pays.
The policy page has no reward table. Here is what it says, in its own words.
- Pays cash
-
Yes
A reward will be paid only after the vulnerability has been verified and confirmed by us.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test.
Domains 1
- tapfiliate.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Tapfiliate B.V.'s policy. "We" in these lines means the program, not this site.
While testing
-
You are strictly prohibited from disclosing any information about the vulnerability to anyone other than the owner – Tapfiliate B.V.
-
DDoS attacks
-
Social engineering
-
Gaining physical access to servers or infrastructure
-
Threats or harm directed at company employees
-
Provide a working proof of concept, preferably with screenshots or a screencast.
-
Clearly specify the affected service or section.
-
Describe the reproduction steps in detail.
Not accepted
-
Brute force attacks, enumeration, and web scraping are not considered valid vulnerabilities and are not rewarded.
-
Use of leaked data from external systems within our platform.
-
Phishing attacks.
-
Attacks that require full administrative access to a user’s account.
-
Vulnerabilities in third-party partner services or products that do not directly impact the security of our own services.
-
Session-related issues (e.g., session fixation, session prediction).
-
Alerts generated by automated security scanners or tools unless accompanied by a verified, real-world proof of exploitability.
-
Reports based solely on software or protocol versions without demonstrating actual impact or exploitation.
-
Logout CSRF, self-XSS, UI redressing (framing), Clickjacking.
-
Open redirect vulnerabilities (e.g., via `/away.php`).
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 12 Nov 2026. Last checked 2 hours 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.