- Top reward
- Not published
- Top severity paid
- Not published
- Assets in scope
- 2
- 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]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 7 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
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.
- Response
-
Within 7 days
We will respond to your report within seven days with an assessment and an expected solution date.
- Safe harbor
-
Full
If you report a vulnerability in one of our ICT systems and follow the above procedure, there will be no legal consequences regarding this report.
- Hall of fame
-
Yes
We can publish your name as the discoverer of the vulnerability if you like.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
2 assets you may test.
Domains 1
- nwbbank.com
Products and areas 1
- our ICT systems
Rules
What the policy asks of you, and the bug types it won't reward, quoted from NWB Bank's policy. "We" in these lines means the program, not this site.
While testing
-
Do not share information on the vulnerability with others until the problems have been resolved.
-
Use your knowledge of the vulnerability responsibly. Do not perform any more actions than necessary to demonstrate the vulnerability.
-
Installing malware.
-
Copying, modifying and/or deleting data in any of our systems (or creating a directory listing of a system).
-
Modifying systems in any way.
-
Repeatedly gaining access to the system or sharing access with others.
-
Using brute-force to gain access to systems.
-
Using denial-of-service or social engineering.
-
Exploiting the vulnerability more than is necessary to establish its presence.
-
Do not publicly announce the vulnerability, but get in touch with us and give us an opportunity to resolve the issue.
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 11 Nov 2026. Last checked 5 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.