Superbank Security

Help us keep banking super safe.

We welcome responsible security research that helps us protect our customers, partners, and the Superbank experience.

Report a security issue

Vulnerability Disclosure Program

Build a safer way to bank, together.

Superbank invites independent security researchers to responsibly disclose vulnerabilities in our in-scope applications and digital assets.

Vulnerability Disclosure Program Scope and Rewards

Know what is in scope.

Only test assets explicitly listed below. Assets not listed are out of scope unless the Superbank Security Team adds them in writing.

In scope

In-scope assets

  • Web applications: all Superbank-owned web assets under *.superbank.id and *.super-id.net.
  • Android application: official Superbank mobile application.
  • iOS application: official Superbank mobile application.
Scope rule. Testing must be limited to the listed Superbank assets, your own accounts, and test data you are authorised to use.

Program rules

Research responsibly.

If you are working on this program, you must follow all of the rules below.

01

You must be the first reporter of a valid vulnerability. Known issues or submissions leading back to the same root cause are duplicates.

02

You are not authorised to access user or company data, including personal data, except the minimum access required to validate a vulnerability.

03

All automated testing traffic must include a clear researcher identifier in the User-Agent using the format `VDP-<name>` and must be rate-limited to avoid service degradation. Requests that do not include this identifier may be blocked to protect platform availability. Please comply with this requirement to prevent disruption to authorised testing activities.

04

Denial-of-service and distributed denial-of-service attacks are prohibited.

05

Public or private disclosure of a vulnerability before written approval from Superbank is prohibited.

06

Never attempt non-technical attacks, including social engineering, phishing, or physical attacks.

07

You must not be a current or former Superbank employee for this public program.

08

Use only accounts and test data that you own or are explicitly authorised to use.

09

Do not brute-force credentials, guess credentials, change another user’s password, or target a specific employee, customer, or partner.

10

Do not leave any system in a more vulnerable state than you found it, destroy data, or download information beyond the minimum needed for your proof of concept.

11

Respect user privacy and confidentiality and comply with all applicable laws and regulations during the research process.

12

In the event of non-compliance, Superbank reserves the right to reject the report and take appropriate legal action.

Reporting terms

Report responsibly.

We encourage our customers, users, security researchers, business partners, and other individuals who interact with Superbank’s services to report suspected or identified vulnerabilities responsibly and in accordance with the terms below.

These terms set out the guidelines for submitting vulnerability reports directly to Superbank. By voluntarily submitting a report, you acknowledge and agree that:

01

You will act in good faith and only perform the minimum testing necessary to confirm the existence of a potential vulnerability.

02

You will not exploit a vulnerability, attempt to gain unauthorised access, or access, modify, delete, or exfiltrate data.

03

You will not disrupt, degrade, or impair the availability or performance of our systems, products, or services.

04

You will not disclose the vulnerability, your report, or the fact that you submitted a report to any third party or to the public without Superbank’s prior written consent.

05

You will promptly stop testing and notify Superbank if you unintentionally access personal, confidential, or proprietary information.

06

Your report is submitted voluntarily and in good faith, without any expectation of payment, compensation, or other reward.

07

To the extent permitted by applicable law, you assign to Superbank all rights and interests in the vulnerability report and related findings, including the right to use, reproduce, assess, and remediate them.

How to report a vulnerability

Give us what we need to help.

If you believe you have identified a security vulnerability or issue affecting Superbank, please submit your report through the designated reporting form below this page.

Please do not include unnecessary personal, confidential, or sensitive information in your submission. If you unintentionally access such information during testing, stop immediately and notify Superbank through the designated reporting channel.

01

A clear description of the suspected vulnerability.

02

The affected product, service, application, or URL.

03

The steps required to reproduce the issue.

04

The potential impact or security risk.

05

Relevant screenshots, logs, proof-of-concept code, or other supporting information.

06

Your contact details so that we can follow up with you.

Testing boundaries

Out of scope.

The following findings and activities are not eligible for reward in this draft program.

Web applications and APIs

  • Broken link or social-media hijacking.
  • Tabnabbing.
  • Missing cookie flags.
  • Content or text injection.
  • Clickjacking or UI redressing.
  • Denial-of-service (DoS) attacks.
  • Recently disclosed CVEs less than 30 days after patch release.
  • CVEs without an exploitable vulnerability and PoC.
  • Open ports or services without an exploitable vulnerability and PoC.
  • Presence of autocomplete attributes on web forms.
  • Vulnerabilities affecting outdated browsers or platforms.
  • Self-XSS or XSS that cannot impact other users.
  • Hypothetical flaws or best-practice findings without an exploitable vulnerability and PoC.
  • SSL/TLS issues such as expired certificates or best-practice findings.
  • Unexploitable vulnerabilities, including Self-XSS, XSS, or Open Redirect through HTTP headers.
  • Missing security-related HTTP headers that do not directly lead to an exploitable vulnerability and PoC.
  • Low-severity CSRF, including unauthenticated, logout, login, or product-cart updates.
  • Invalid or missing SPF, DKIM, or DMARC records.
  • Session-management issues such as expiration, logout-on-password-change, or concurrent-session behavior without exploitable impact.
  • Information disclosure without an exploitable vulnerability and PoC, including stack traces, paths, directory listings, versions, IPs, third-party secrets, or EXIF metadata.
  • CSV injection.
  • Malicious file uploads such as EICAR files or executable files.
  • HTTP Strict Transport Security (HSTS) findings.
  • Subdomain takeover without a fully exploitable vulnerability and PoC or where not applicable to scope.
  • Blind SSRF without an exploitable vulnerability and PoC, including DNS or HTTP pingbacks.
  • Missing or bypassable rate limits, brute force, or CAPTCHA issues.
  • User enumeration, including email, alias, GUID, phone number, or common CMS endpoints.
  • Weak password policies involving length, complexity, or reuse.
  • Ability to spam users through email, SMS, or direct-message flooding.
  • Disclosed or misconfigured public API keys for non-sensitive services such as maps, Firebase, or analytics.
  • Password-reset tokens sent through HTTP Referer to external services.
  • Secrets, credentials, or information gathered from third-party assets outside Superbank control.
  • Exposed secrets, credentials, or information on an asset under Superbank control that is outside program scope.
  • Pre-account takeover, including account creation through OAuth.
  • GraphQL introspection enabled without an exploitable impact.
  • Task hijacking.
  • Crashing your own application.

Mobile applications

  • Missing client-side protections in mobile binaries, including SSL pinning, binary protection, code obfuscation, jailbreak/root detection, or anti-debugging controls.
  • Lack of encryption on internal mobile databases or preference files.
  • Exploits possible only on Android versions not supported at the time of the report.
  • Exploits possible only on iOS versions not supported at the time of the report.
  • Exploits possible only on a jailbroken or rooted device.
  • Generic Android or iOS vulnerabilities without a Superbank-specific exploitable impact and PoC.

General restrictions

  • Social engineering of staff or contractors.
  • Attack scenarios requiring a man-in-the-middle (MITM) position or physical access to a victim device.
  • Any issue without a reproducible, exploitable security impact and PoC.
Important. Do not test or target Superbank employees, customers, partners, service desks, or third-party infrastructure. When uncertain, ask before testing.

Reward matrix

Impact matters.

Superbank will only reward the first reporter of a valid vulnerability that is in scope and reported in compliance with this policy.

Superbank only processes report reward payments via bank transfer to the registered Superbank account.

Vulnerability Disclosure Program reward matrix
SeverityReward
Critical USD 1,000–2,000
High USD 700–1,000
Medium USD 400–700
Low USD 50–100

Ready to report?

Tell us what you found.

Use the reporting form to provide clear reproduction steps, impact, screenshots or video PoC where applicable, and the test account or data context used.

Open reporting form

Submit vulnerability reports through the secure reporting form.

Contactoffensive@superbank.id