avatar
Bug bounty
Public

Superbank - Public Bug Bounty Program

Superbank is digital bank from Indonesia.

Reward

Bounty
Hall of fame
$50
Low
$150
Medium
$1,000
High
$3,000
Critical
$6,000

Program

Avg reward
-
Max reward
-

Scopes
6
Supported languages
English
Indonesian

Hacktivity

Reports
25
1st response
< 1 day
Reports last 24h
25
Reports last week
25
Reports this month
25

Superbank

Superbank is a prominent digital banking platform in Indonesia, known for providing innovative, customer-centric banking services powered by advanced technology. It aims to redefine banking experiences by offering seamless, easy-to-use services through mobile and online platforms. For now, Superbank as a digital banking in indonesia is created a bug bounty program with the scope and a program rules below.

Scopes description

Android & iOS

This app is critical to our business as it's where the user use our mobile banking application.The app allows users to perform a wide range of banking activities directly from their mobile devices, making it a convenient tool for managing finances on the go.

API

This API is critical to our business as it's where the user use our services on our environment.

Web Application

This application is our company profile and our ecosystem webview where user find any information regarding our bussiness and register on our application.

Program Rules

Testing Policy, Responsible Disclosure

Please adhere to the following rules while performing research on this program:

  • Denial of service (DoS) attacks on Superbank applications, servers, networks or infrastructure are strictly forbidden.
  • Avoid tests that could cause degradation or interruption of our services.
  • Do not use automated scanners or tools that generate large amount of network traffic
  • Do not leak, copy, manipulate, or destroy any user data or files in any of our applications/servers.
  • No vulnerability disclosure, full, partial or otherwise, is allowed.

Important precautions and limitations

As a complement to the Program’s rules and testing policy :

  • DO NOT alter compromised accounts by creating, deleting or modifying any data
  • DO NOT use compromised accounts to search for post-auth vulnerabilities (they won’t be eligible anyway)
  • DO NOT include Personally Identifiable Information (PII) in your report and please REDACT/OBFUSCATE the PII that is part of your PoC (screenshot, server response, JSON file, etc.) as much as possible.
  • In case of exposed credentials or secrets, limit yourself to verifying the credentials validity
  • In case of sensitivie information leak, DO NOT extract/copy every document or data that is exposed and limit yourself to describe and list what is exposed.

Reward Eligibility

We are happy to thank everyone who submits valid reports which help us improve the security of Superbank, however only those that meet the following eligibility requirements may receive a monetary reward:

  • You must be the first reporter of a vulnerability.
  • The vulnerability must be a qualifying vulnerability
  • The report must contain the following elements:
    • Clear textual description of the vulnerability, how it can be exploited, the security impact it has on the application, its users and Superbank, and remediation advice on fixing the vulnerability
    • Proof of exploitation: screenshots/video demonstrating the exploit was performed, and showing the final impact
    • Provide complete steps with the necessary information to reproduce the exploit, including (if necessary) code snippets, payloads, commands etc
  • You must not break any of the testing policy rules listed above
  • You must not be a former or current employee of Superbank, Grab, OVO, GxS, GxB or one of its contractors.

Reward amounts are based on:

  • Reward grid of the report's scope
  • CVSS scoring and actual business impact of the vulnerability upon performing risk analysis

Reward

Asset value CVSS
Low
CVSS
Medium
CVSS
High
CVSS
Critical
High
$150$1,000$3,000$6,000
Medium
$100$800$2,000$4,000

Systemic issues

1st report100%
2nd report100%
3rd report75%
4th report50%
5th report25%
6th+ report10%

In the context of this program, we do not intend to encourage, accept or reward reports of leaks that are not applicable to our program’s scope and policy. To summarize our policy, you may refer to the below table:


Scopes

ScopeTypeAsset value
https://apps.apple.com/id/app/superbank/id6444720285
Mobile application IOS
High
Low
$150
Medium
$1,000
High
$3,000
Critical
$6,000
https://play.google.com/store/apps/details?id=id.co.bankfama.android&hl=en
Mobile application Android
High
Low
$150
Medium
$1,000
High
$3,000
Critical
$6,000
*.superbank.id
API
High
Low
$150
Medium
$1,000
High
$3,000
Critical
$6,000
*.super-id.net
API
High
Low
$150
Medium
$1,000
High
$3,000
Critical
$6,000
https://www.superbank.id/
Web application
Medium
Low
$100
Medium
$800
High
$2,000
Critical
$4,000
https://ecosystem-experience.super-id.net
Web application
Medium
Low
$100
Medium
$800
High
$2,000
Critical
$4,000

Out of scopes

  • Applications, URLs, or data that are not listed on this page are considered out of scope.

Vulnerability types

Qualifying vulnerabilities

  • SQL Injection (SQLi)
  • Cross-Site Scripting (XSS)
  • Remote Code Execution (RCE)
  • Insecure Direct Object Reference (IDOR)
  • Horizontal and vertical privilege escalation
  • Authentication bypass & broken authentication
  • Business Logic Errors vulnerability with real security impact
  • Local files access and manipulation (LFI, RFI, XXE, SSRF, XSPA)
  • Cross-Origin Resource Sharing (CORS) with real security impact
  • Cross-site Request Forgery (CSRF) with real security impact
  • Open Redirect
  • Remote silent installation of any app
  • Other severe logic vulnerabilities that can be exploited remotely
  • Arbitrary code execution (ACE)
  • Sensitive information leakages
  • Privilege escalation vulnerabilities
  • Vulnerabilities able to break the site isolation restrictions of a browser
  • Arbitrary code execution or silent installation by staging MITM attacks
  • Leakages of common information
  • Remote denial of service vulnerability
  • Stealing of sensitive information by staging MITM attacks
  • UI deception vulnerabilities that may cause actual harm

Non-qualifying vulnerabilities

  • Tabnabbing
  • Missing cookie flags
  • Content/Text injections
  • Mixed content warnings
  • Clickjacking/UI redressing
  • Denial of Service (DoS) attacks
  • Known CVEs without working PoC
  • Open ports without real security impact
  • Social engineering of staff or contractors
  • Presence of autocomplete attribute on web forms
  • Vulnerabilities affecting outdated browsers or platforms
  • Self-XSS or XSS that cannot be used to impact other users
  • Outdated libraries without a demonstrated security impact
  • Any hypothetical flaw or best practices without exploitable PoC
  • Expired certificate, best practices and other related issues for TLS/SSL certificates
  • Unexploitable vulnerabilities (ex: XSS or Open Redirect in HTTP Host Header)
  • Missing security-related HTTP headers which do not lead directly to a vulnerability
  • Unauthenticated / Logout / Login and other low-severity Cross-Site Request Forgery (CSRF)
  • Invalid or missing SPF (Sender Policy Framework), DKIM, DMARC records
  • Session expiration policies (no automatic logout, invalidation after a certain time or after a password change)
  • Disclosure of information without direct security impact (e.g. stack traces, path disclosure, directory listings, software versions, IP disclosure, 3rd party secrets)
  • CSV injection
  • HTTP Strict Transport Security Header (HSTS)
  • Subdomain takeover without a full working PoC
  • Blind SSRF without direct impact (e.g. DNS pingback)
  • Lack of rate-limiting, brute-forcing or captcha issues
  • User enumeration (email, alias, GUID, phone number)
  • Password requirements policies (length / complexity / reuse)
  • Ability to spam users (email / SMS / direct messages flooding)
  • Disclosed / misconfigured Google API key (including Google Maps)
  • Recently disclosed 0-day vulnerabilities (less than 90 days since patch release)
  • Password reset token leak on trusted third-party website via Referer header (eg Google Analytics, Facebook…)
  • Task Hijacking
  • Crashing your own application
  • Google API Keys (eg. Analytics, Maps)
  • Lack of code obfuscation / binary protection
  • Exploiting a generic Android or iOS vulnerability
  • Information requiring physical access to user device
  • Exploits that are only possible on rooted/jailbroken device
  • Exploits that are only possible on iOS version 10 and below
  • Exploits that are only possible on Android version 7 and below
  • Lack of encryption on internal databases/preference files on mobile device
  • Vulnerabilities affecting outdated application binaries - only exploits working on latest Android/iOS versions from the respective app stores will be accepted
  • Lack of client-side protections on mobile binaries: SSL pinning/binary protection/code obfuscation/jailbreak detection/root detection/anti-debugging controls/ etc

Reports of leaks and exposed credentials

In the context of this program, we do not intend to encourage, accept or reward reports of leaks that are not applicable to our program’s scope and policy. To summarize our policy, you may refer to the below table:

Type of leak
Source of leak is in-scope
Source of leak belongs to the Organization and is out-of-scope
Source of leak does not belong to the Organization and is out-of-scope
Impact is in-scope (e.g. valid credentials on an in-scope asset)
checked Eligible
checked Eligible
checked Not eligible
Impact is out-of-scope (e.g. valid credentials for an out-of-scope asset)
checked Eligible
checked Not eligible
checked Not eligible

Hunting requirements

Account access

Self-register

Superbank Scope

  • You can self-register from Android OR iOS .
  • Please use your YesWeHack email aliases which are available here for account creation.
  • The use of a personal account is authorized if you have one.

API

  • *.superbank.id
  • *.super-id.net

Web

  • https://www.superbank.id/
  • https://ecosystem-experience.super-id.net

Hunters collaboration

When submitting new report, you can add up to 5 collaborators, and define the reward split ratio.

For more information, see help center.
Note: For reports that have already been rewarded, it is not possible to redistribute the rewards.

To submit a vulnerability report, you need to login with your hunter account.