- Top reward
- $10,000
- Top severity paid
- Critical
- Assets in scope
- 17
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to $10,000
- for critical bugs.
- Report on HackerOne
- Submit through the program page.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What HackerOne lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$10,000 from $3,000 |
| High |
|
$6,000 from $1,250 |
| Medium |
|
$2,000 from $500 |
| Low |
|
$300 |
Scope
17 assets you may test, 2 excluded.
Web 15
- accountshomolog.acesso.io Critical
- api.humantoken.unico.app Critical
- backend-sdk.uat.private.unico.run Critical
- blog.unico.io Medium
- dashboard.unico.app Critical
- developer.unico.io Medium
- https://sdk-h1.unico.io/createprocess Critical
- humantoken.unico.app Critical
- idcash-uat.unico.io Critical
- identityhomolog.acesso.io Critical
- idpay-uat.unico.io Critical
- issuer.idpay-uat.unico.io Critical
- openfinance.unico.io Critical
- secure.unico.io Critical
- unico.io Critical
Wildcard domains 1
- *.uat.unico.app Critical
Products and areas 1
- [Unico] Liveness Bypass Critical
Out of scope (2)
- uconf.uat.unico.app
- *.cadastro.uat.unico.app
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Unico IDtech (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.
-
Ask the program team **before submitting vulnerabilities on unscoped subdomains**
-
Only interact with accounts you own or with the explicit permission of the account holder.
Not accepted
-
Clickjacking on pages with no sensitive actions
-
Attacks on authentication tokens without impact (e.g., expiration time).
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms without confidential actions.
-
Attacks requiring Man-in-the-Middle (MITM) or physical access to a user's device.
-
Vulnerable libraries previously known without a functional Proof of Concept.
-
File uploads without impact or execution of malicious code.
-
Injection of comma-separated values (CSV) without demonstrating a vulnerability.
-
Lack of best practices in SSL/TLS configuration.
-
Any activity that could lead to disruption of our service (DoS).
-
Content spoofing and text injection issues without showing an attack vector/unable to modify HTML/CSS.
-
Rate limiting or brute force issues on endpoints without authentication.
-
Lack of best practices in Content Security Policy.
-
Missing HttpOnly or Secure flags on cookies.
-
Missing controls (invalid, incomplete, or missing SPF/DKIM/DMARC records, etc.).
-
Vulnerabilities affecting only users of outdated or unpatched browsers.
-
Disclosure of software version/Issues with banner identification/Descriptive error messages or headers (e.g., stack traces, application or server errors).
-
Open redirection - unless an additional security impact can be demonstrated.
-
Issues requiring unlikely user interaction.
-
Self-XSS or DOM XSS without clear impact.
-
Service banner and/or version.
-
Any bug depending on an outdated browser.
-
Exposed credentials that are either no longer valid or do not represent a risk to an asset in scope.
-
Domain/Subdomain takeover.
-
Broken links, typos, or content issues on static, institutional, or marketing pages.
Summarised with AI from the program policy on HackerOne, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 1 hour ago.
-
Scope +
Added to scope: developer.unico.io
-
Scope +
Added to scope: humantoken.unico.app
-
Scope +
Added to scope: api.humantoken.unico.app
-
Scope +
Added to scope: dashboard.unico.app
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope added
developer.unico.io
-
Scope removed
devcenter.unico.io
-
Scope added
humantoken.unico.app
-
Scope added
api.humantoken.unico.app
-
Scope added
dashboard.unico.app
-
Reward terms
High $5,000 → $6,000
-
Rules updated
Added: “> ⚠️ **Notice:** Video and Image Replay submissions are temporarily suspended. Reports submitted during this period will be closed as Informative and will not b...”
-
Rules updated
Added: “> ⚠️ **Notice:** Video Replay submissions are temporarily suspended while this vector is under active internal remediation. Reports submitted during this period...”
-
Scope added
uconf.uat.unico.app (out of scope)
-
Scope added
accountshomolog.acesso.io
-
Scope added
backend-sdk.uat.private.unico.run
-
Scope added
identityhomolog.acesso.io
-
Scope added
[Unico] Liveness Bypass
-
Scope added
blog.unico.io
-
Scope added
idcash-uat.unico.io
-
Scope added
idpay-uat.unico.io
-
Scope added
issuer.idpay-uat.unico.io
-
Scope added
openfinance.unico.io
-
Scope added
secure.unico.io
-
Scope added
unico.io
-
Scope added
*.uat.unico.app
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.
Unico IDTech Bug Bounty Program
Unico IDTech is pioneering the future of biometric authentication through our advanced liveness detection engine. We're inviting security researchers to help protect millions of digital identities by finding novel ways to bypass our state-of-the-art biometric controls.
Applicability
The Bug Bounty program is now public and open to all security researchers. The following groups are not eligible:
- Employees and former employees of Unico IdTech or its subsidiary companies;
- First-degree relatives of employees of Unico IdTech or its subsidiaries or affiliates;
- Third parties who have access to the Organization's confidential information;
Disclosure Policy
- Please do not publicly disclose vulnerabilities until they have been resolved and we have provided explicit consent for disclosure.
- Follow HackerOne's disclosure guidelines.
Program Rules
- 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.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
- Ask the program team before submitting vulnerabilities on unscoped subdomains
- Only interact with accounts you own or with the explicit permission of the account holder.
Structure and Focus of the program
Our Bug Bounty program is divided into two distinct scopes: Liveness and Web. Each scope targets specific areas of our systems, with a ==primary focus on testing the security controls associated with the Liveness scope==.
Primary scope - Liveness
Report only if you were able to bypass liveness detection and obtained a live:true status at the end of the transaction.
For more details, please refer to IDCloud - DevCenter.
⚠️ Notice: Video and Image Replay submissions are temporarily suspended. Reports submitted during this period will be closed as Informative and will not be eligible for bounty.
Presentation Attack Detection Matrix
| Test Type | Success Criteria | Failure Criteria | When to Report |
|---|---|---|---|
| Photo Attack | Engine accepts static image as live | Engine correctly rejects static image | Report if bypass rate >1% over 100 attempts |
| Suspended — see notice above. | |||
| 3D Mask/Model | Engine accepts non-human presentation | Engine detects artificial surface | Report if any high-quality mask achieves >5% success rate |
| Deepfake | Engine accepts syntethic video stream | Engine detects manipulation artifacts | Report if real-time bypass achieved with <500ms latency |
Processing Integrity Matrix
| Test Type | Success Criteria | Failure Criteria | When to Report |
|---|---|---|---|
| Memory Manipulation | Modified engine parameters accepted | Tampering detected and rejected | Report if persistence across engine restarts |
| Template Injection | Artificial template processed as valid | Invalid template detected | Report if bypass work on multiple formats |
| Timing Attacks | Processing bypass through race condition | Proper sequence validation | Report if reproducible >50% of attempts |
Data Flow Integrity Matrix
| Test Type | Success Criteria | Failure Criteria | When to Report |
|---|---|---|---|
| Capture Relay | Reused biometric data accepted | Replay detected and blocked | Report if bypass works across sessions |
| Stream Manipulation | Modified data stream processed as valid | Data integrity check failure | Report if manipulation undetected by engine |
| Session Hijacking | Authentication state transferred | Session binding enforced | Report if state can be copied between instances |
Reporting Liveness Bypasses
Report when the SDK returns a positive liveness result for a presentation attack, following the criteria in the matrices above. Include Transaction ID and Process ID. Our team will validate the full bypass chain including backend verification.
The testing will focus on the biometric SDK, not the wrapper applications. The test applications serve solely to facilitate SDK testing and are out of scope. Vulnerabilities related to the biometric capture and processing engine are in scope, while issues related to the wrapper interface or presentation layer are out of scope.
Report Requirements
- When reporting a vulnerability, it is essential to include the Transaction ID and the Process ID of capture.
Severity Assessment
Severity for Liveness findings is determined by two primary factors: novelty and exploitability.
Novelty reflects whether the core technique or a key step in the exploitation chain has been previously identified by the program — whether through prior researcher submissions or internal security assessments. Techniques already known to the program will be weighed accordingly in the severity assessment.
Exploitability reflects how realistic and reproducible the attack is under standard conditions. Findings that work on unmodified devices without special hardware or elevated privileges are rated higher than those that require a rooted device, a modified application binary, or other controlled prerequisites.
| Severity | Criteria |
|---|---|
| Critical | live:true confirmed via a technique not previously reported to or communicated by the program, demonstrated under realistic conditions without significant prerequisites. |
| High | live:true confirmed, but one or more key steps in the exploitation chain were previously identified by the program; or the bypass requires significant prerequisites (modified binary, specialized hardware). |
| Medium | Finding that demonstrates a meaningful gap in liveness controls but does not independently achieve live:true. |
| Low | Auxiliary finding related to liveness infrastructure that could contribute to an attack chain but does not independently bypass liveness detection. |
Useful Links for Testing Liveness
System Requirements:
- Web: Modern browser (Chrome, Firefox, Safari, or Edge) with camera access
- Android: Physical device with Android 6.0 (API 23) or higher
- iOS: Physical device with iOS 14.0 or higher
Web Testing: Web testing can be performed in any modern browser.
Physical Devices Required for Mobile Testing: The mobile applications (Android Native, iOS Native, Android Flutter, and iOS Flutter) DO NOT work on emulators or simulators. You must use physical devices for mobile testing.
Application Expiration (TTL): The mobile applications have a 30-day Time-To-Live (TTL). If the app stops working or shows expiration errors, download and install the latest version from the links above. Web application does not expire.
Recommended Testing Approach: We strongly recommend using the native apps (Android Native and iOS Native) for mobile testing. The native apps offer smoother performance and more direct SDK integration. Flutter apps are provided for convenience but use the native SDKs as a bridge layer.
Changelog
Secondary scope - Web
| Vulnerability Type | When to report a problem |
|---|---|
| XSS | A simple alert(document.domain) is enough. |
| RCE | Please only run harmless code. Simply printing something or evaluating an expression should be enough to demonstrate the problem. |
| SQLi | Please report it as soon as you experience a SQL error that indicates SQL injection or you are able to disclose the SQL server version number. |
| SSRF | Do not play on any internal networks. Let us know as soon as you believe you have a possible SSRF issue and we will look into it for you. |
| JWT Tokens Vulnerabilities | Injecting self-signed tokens or breaking authorization controls. |
| IDOR | Access confidential information from another user/organization or users with greater privileges. |
| Unrestricted File Upload | Upload a simple shell, a file with an extension or content-type different from those requested. |
Severity Assessment
Severity for Web findings is assessed holistically based on multiple factors: exploitability (how feasible the attack is in practice), impact (the actual consequence for users or the organization), attack complexity, and required access level. The program team evaluates each finding on its own context — a technically exploitable issue with limited real-world impact may be rated lower than its CVSS score suggests, and vice versa.
Researchers are encouraged to include a CVSS 3.1 score and an OWASP Risk Rating assessment as references. Final severity is determined by the program team.
Using the OWASP Risk Rating calculator will be greatly appreciated.
Session Layer: HTTP Headers
Researchers should add headers to requests such as:
- "X-HackerOne-Research: [H1 username]"
- "User-Agent: [H1 username]"
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:
- Clickjacking on pages with no sensitive actions
- Attacks on authentication tokens without impact (e.g., expiration time).
- Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms without confidential actions.
- Attacks requiring Man-in-the-Middle (MITM) or physical access to a user's device.
- Vulnerable libraries previously known without a functional Proof of Concept.
- File uploads without impact or execution of malicious code.
- Injection of comma-separated values (CSV) without demonstrating a vulnerability.
- Lack of best practices in SSL/TLS configuration.
- Any activity that could lead to disruption of our service (DoS).
- Content spoofing and text injection issues without showing an attack vector/unable to modify HTML/CSS.
- Rate limiting or brute force issues on endpoints without authentication.
- Lack of best practices in Content Security Policy.
- Missing HttpOnly or Secure flags on cookies.
- Missing controls (invalid, incomplete, or missing SPF/DKIM/DMARC records, etc.).
- Vulnerabilities affecting only users of outdated or unpatched browsers.
- Disclosure of software version/Issues with banner identification/Descriptive error messages or headers (e.g., stack traces, application or server errors).
- Open redirection - unless an additional security impact can be demonstrated.
- Issues requiring unlikely user interaction.
- Self-XSS or DOM XSS without clear impact.
- Service banner and/or version.
- Any bug depending on an outdated browser.
- Exposed credentials that are either no longer valid or do not represent a risk to an asset in scope.
- Domain/Subdomain takeover.
- Discrepancies between content stated in privacy policies, terms of use, or institutional pages and the actual application behavior (transparency or compliance concerns should be reported through Unico's privacy/DPO channels).
- Broken links, typos, or content issues on static, institutional, or marketing pages.
Thank you for helping keep Unico IDtech and our users safe!