- Top reward
- $5,000
- Top severity paid
- Critical
- Assets in scope
- 8
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $5,000
- for critical bugs.
- Report on HackerOne
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 5 days
- As the policy promises.
Rewards
What HackerOne lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$5,000 |
| High |
|
$2,000 |
| Medium |
|
$1,000 |
| Low |
|
$500 from $100 |
- Response
-
Within 5 days
Time to first response (from report submit) - 5 business days
- Safe harbor
-
Full
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
8 assets you may test.
Web 6
- digili.s-cloud.fi Critical
- extranet.s-pankki.fi Critical
- https://crosskey.io/stores/s-pankki/apis Critical
- mobile.s-pankki.fi Critical
- online.s-pankki.fi Critical
- www.s-pankki.fi Critical
Android apps 1
- fi.spankki Critical
iOS apps 1
- 740514933 Critical
Rules
What the policy asks of you, and the bug types it won't reward, quoted from S-Pankki (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
-
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
-
When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
-
Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
-
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
-
We run our program in English and all reports should be submitted in English.
-
Please do not perform brute force testing to determine whether rate limiting is in place for particular APIs or pieces of functionality.
-
Denial of Service attacks
-
Physical attacks against offices and data centers
-
Social engineering (e.g. phishing, vishing, smishing) of our service desk, employees or contractors
Not accepted
-
Self-XSS and XSS without impact
-
Clickjacking on pages with no sensitive actions
-
Unauthenticated CSRF
-
Attacks requiring MITM or physical access to a user's device (MITM in mobile applications are in-scope but those are reviewed case by case)
-
Previously known vulnerable libraries without a working Proof of Concept
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability
-
Any activity that could lead to the disruption of our service (DoS).
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 5 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 hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
S-Pankki Bug Bounty Program
S-Pankki looks forward to working with the security community to find security vulnerabilities in order to keep our businesses, systems and customers safe.
Program Rules
Our bug bounty program is limited strictly to technical security vulnerabilities of S-Pankki services listed in the scope. Any activity that would disrupt, damage or adversely affect any data or account is not allowed.
These program rules are:
- Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
- When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
- Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
- We run our program in English and all reports should be submitted in English.
- S-Pankki has all rights to make bounty policy changes at any time without prior notification.
- S-Pankki has right to discontinue the bug bounty program at any time without prior notification.
- Employees from following companies are not allowed to participate to the bugbounty program: S-Pankki, S-Group, Crosskey, HiQ, Nitor, WithSecure, F-Secure, Reversec, Comiq, Solita, Reaktor, Taitopilvi, Vaimo, Solteq, Frantic, New Things Co, KnowIT, Digia, Columbia Road, Vala Group,Taito United, Gofore and Netlight.
Please do not perform brute force testing to determine whether rate limiting is in place for particular APIs or pieces of functionality.
The following actions are strictly prohibited:
- Denial of Service attacks
- Physical attacks against offices and data centers
- Social engineering (e.g. phishing, vishing, smishing) of our service desk, employees or contractors
- Compromise of a S-Pankki user's or employee's account
- Automated tools or scans, botnet, compromised site, end-clients or any other means of large automated exploitation or use of a tool that generates a significant volume of traffic
Additionally, the vulnerabilities listed in the section below will not be considered for bounty.
Out-of-scope vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug.
The following issues are considered out of scope:
- Self-XSS and XSS without impact
- Clickjacking on pages with no sensitive actions
- Unauthenticated CSRF
- Attacks requiring MITM or physical access to a user's device (MITM in mobile applications are in-scope but those are reviewed case by case)
- Previously known vulnerable libraries without a working Proof of Concept
- Comma Separated Values (CSV) injection without demonstrating a vulnerability
- Any activity that could lead to the disruption of our service (DoS).
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
SLA
S-Pankki will make a best effort to meet the following SLAs for hackers participating in our program:
- Time to first response (from report submit) - 5 business days
- Time to triage (from report submit) - 10 business days
- Time to bounty (from triage) - 10 business days
We’ll try to keep you informed about our progress throughout the process.
Data Protection
S-Pankki may receive personal data in relation to use of Bug Bounty program and shall adhere the EU General Data Protection Regulation (GDPR) and other applicable legislation.
Whenever personal data is encountered during testing, S-Pankki expects and requires all persons involved to handle that data with utmost care. Showing or proving the existence of a flaw does likely not require any data dumps - so even if possible, no dumping of personal data is allowed. Any exfiltrated personal data must immediately be deleted and any testing that might result in further personal data being revealed must be halted. You shall not store personal data. Personal data samples, if needed in the report, shall be properly obfuscated before posting. This includes submitting reports that contain your own data. In the case where personal data is posted in a report we will redact that information as soon as possible. If after the redaction the report is unintelligible, it will not be processed.
Safe Harbor
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
Thank you for helping keep S-Pankki and our users safe!