AMLBot Web
By AMLBot Bug bounty on HackenProof amlbot.com
- Top reward
- $500
- Top severity paid
- Critical
- Assets in scope
- 1
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $500
- for critical bugs.
- Report on HackenProof
- Submit through the program page.
- Replies within 3 days
- As the policy promises.
- Payment
- Proof of identity needed to get paid.
- No public write-ups
- Keep findings private.
Rewards
What HackenProof lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$500 |
- Response
-
Within 3 days
First Response 3d
- Hall of fame
-
Yes
@holybugx KYC 1
Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test, 2 excluded.
Web 1
- https://kyc-bounty.amlbot.com
Out of scope (2)
- Assets that do not belong to the company
- Vulnerabilities in third-party applications
Rules
What the policy asks of you, and the bug types it won't reward, quoted from AMLBot Web (via HackenProof)'s policy.
While testing
-
Avoid using web application scanners for automatic vulnerability searching which generates massive traffic
-
Make every effort not to damage or restrict the availability of products, services, or infrastructure
-
Don’t access or modify other user data, localize all tests to your accounts
-
Perform testing only within the scope
-
Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
-
Don’t break any law and stay in the defined scope
-
Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission
-
All communication regarding the program must take place exclusively through the HackenProof platform.
-
Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
-
ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded)
Not accepted
-
Best practices concerns
-
Social engineering, phishing, physical, or other fraud activities
-
Publicly accessible login panels without proof of exploitation
-
Reports generated by scanners or any automated or active exploit tools
-
Denial of service (DoS/DDoS)
-
Theoretical issues
-
Moderately Sensitive Information Disclosure
-
Spam (sms, email, etc)
-
Missing HTTP security headers
-
Open redirects
-
Session fixation
-
User account enumeration
-
Clickjacking/Tapjacking and issues only exploitable through clickjacking/tapjacking
-
Descriptive error messages (e.g. Stack Traces, application or server errors)
-
Self-XSS that cannot be used to exploit other users
-
Login & Logout CSRF
-
Weak Captcha/Captcha Bypass
-
Lack of Secure and HTTPOnly cookie flags
-
OPTIONS/TRACE HTTP method enabled
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
-
Reflected File Download (RFD)
-
Mixed HTTP Content
-
Manipulation with Password Reset Token
-
MitM and local attacks
-
Response manipulations without demonstration of system state change
Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 33 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 hackenproof.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Bug bounty Triaged by HackenProof AMLBot Web: Program info AMLBot Web Company: AMLBot Scope Review: 318933 Submissions: 157 Total rewards: $500 Reputation 100 points required PoC Required Program is: active now Live Submit report Program info Hackers 99 Reports 0 Online assessment of crypto addresses and transactions, founded in 2019 by a team of RegTech specialists in accordance with FATF international recommendations All Scope Focus Area Program Rules Eligibility and Coordinated Disclosure Disclosure Guidelines Scope Search targets In scope Target │ Type │ Severity https://kyc-bounty.amlbot.com Copy Web │ Critical Focus Area IN SCOPE VULNERABILITIES We are interested in the following vulnerabilities: Business logic issues Payments manipulation Remote code execution (RCE) Injection vulnerabilities (SQL, XXE) File inclusions (Local & Remote) Access Control Issues (IDOR, Privilege Escalation, etc) Leakage of sensitive information Server-Side Request Forgery (SSRF) Cross-Site Request Forgery (CSRF) Cross-Site Scripting (XSS) Directory traversal Other vulnerabilities with a clear potential loss OUT OF SCOPE: WEB VULNERABILITIES Vulnerabilities found in out of scope resources are unlikely to be rewarded unless they present a serious business risk (at our sole discretion). In general, the following vulnerabilities do not correspond to the severity threshold: Vulnerabilities in third-party applications Assets that do not belong to the company Best practices concerns Recently (less than 30 days) disclosed 0day vulnerabilities Vulnerabilities affecting users of outdated browsers or platforms Social engineering, phishing, physical, or other fraud activities Publicly accessible login panels without proof of exploitation Reports that state that software is out of date/vulnerable without a proof of concept Reports generated by scanners or any automated or active exploit tools Vulnerabilities involving active content such as web browser add-ons Most brute-forcing issues without clear impact Denial of service (DoS/DDoS) Theoretical issues Moderately Sensitive Information Disclosure Spam (sms, email, etc) Missing HTTP security headers Infrastructure vulnerabilities, including: Certificates/TLS/SSL-related issues; DNS issues (i.e. MX records, SPF records, DMARC records etc.); Server configuration issues (i.e., open ports, TLS, etc.) Open redirects Session fixation User account enumeration Clickjacking/Tapjacking and issues only exploitable through clickjacking/tapjacking Descriptive error messages (e.g. Stack Traces, application or server errors) Self-XSS that cannot be used to exploit other users Login & Logout CSRF Weak Captcha/Captcha Bypass Lack of Secure and HTTPOnly cookie flags Username/email enumeration via Login/Forgot Password Page error messages CSRF in forms that are available to anonymous users (e.g. the contact form) OPTIONS/TRACE HTTP method enabled Host header issues without proof-of-concept demonstrating clear security impact Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS Content Spoofing without embedded links/HTML Reflected File Download (RFD) Mixed HTTP Content HTTPS Mixed Content Scripts Manipulation with Password Reset Token MitM and local attacks Response manipulations without demonstration of system state change Program Rules Avoid using web application scanners for automatic vulnerability searching which generates massive traffic Make every effort not to damage or restrict the availability of products, services, or infrastructure Avoid compromising any personal data, interruption, or degradation of any service Don’t access or modify other user data, localize all tests to your accounts Perform testing only within the scope Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam Don’t spam forms or account creation flows using automated scanners In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity. Don’t break any law and stay in the defined scope Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission All communication regarding the program must take place exclusively through the HackenProof platform. Contacting the project team directly through support channels, social media, or any other external communication channels is strictly prohibited. Researchers who violate this rule may be disqualified from the program and may face account suspension. Eligibility and Coordinated Disclosure We are happy to thank everyone who submits valid reports which help us improve the security. 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 Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary. You must not be a former or current employee of us or one of its contractor. ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded) Provide detailed but to-the point reproduction steps Disclosure Guidelines Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization No vulnerability disclosure, including partial is allowed for the moment. Please do NOT publish/discuss bugs Live since 09 Dec 2025 Published date 09 Dec 2025 Last updated 02 Oct 2026 Range of bounty $50 - $500 Severity Critical $500 High $200 Medium $100 Low $50 Web2 Web @holybugx KYC 1 @web3x2 KYC Verified 2 @paktiko KYC Verified 3 @sunfavy Verified 4 @sendik Verified 5 Response type Business days First Response 3d Triage Time 3d Reward Time 3d Resolution Time 14d