Skip to content

AlphaSec Web & Smart Contracts

By Kaia Bug bounty on HackenProof alphasec.trade

Paused KYC to get paid DEX Solidity Web
Top reward
$10,000
Top severity paid
Critical
Assets in scope
6
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $10,000
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 Reward
Critical $10,000
Response
Within 3 days First Response 3d

Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

6 assets you may test, 2 excluded.

Smart contracts 4

  • https://kaiascan.io/address/0x35Be945fb1da550a76f1FAD6D3759437d71bA739
  • https://kaiascan.io/address/0xe011c8DeaB65F2e299D5fbaa3808E953Ca93ee42
  • https://kaiascan.io/address/0xe4CD7C744C8016a8E42336c91366fB78a192F426
  • https://kaiascan.io/address/0xF31CE581A8440f0f4850eDEb343a28372572a088

Web 1

  • https://alphasec.trade

Wildcard domains 1

  • *.alphasec.trade
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 AlphaSec Web & Smart Contracts (via HackenProof)'s policy. "We" in these lines means the program, not this site.

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 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
  • Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com

Not accepted

  • 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
  • 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

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 1 hour 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.

Search 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 AlphaSec Web & Smart Contracts: Program info AlphaSec Web & Smart Contracts Company: Kaia Scope Review: 304377 Submissions: 174 Total rewards: $25,600 Reputation 150 points required KYC Required PoC Required Program left: 45 days ago Finished Submit report Contest is not active Program info Hackers 89 Reports 0 Alpha Sec. is a high-performance orderbook DEX that brings centralized-level execution into a fully decentralized environment, without compromise. All Scope Focus Area Program Rules Eligibility and Coordinated Disclosure Disclosure Guidelines Scope Search targets In scope Target │ Type │ Severity https://alphasec.trade Copy Web │ High *.alphasec.trade Copy Web │ High https://kaiascan.io/address/0xe4CD7C744C8016a8E42336c91366fB78a192F426 Copy Inbox │ Smart Contract │ Critical https://kaiascan.io/address/0x35Be945fb1da550a76f1FAD6D3759437d71bA739 Copy L1 Gateway Router │ Smart Contract │ Critical https://kaiascan.io/address/0xe011c8DeaB65F2e299D5fbaa3808E953Ca93ee42 Copy Sequencer Inbox │ Smart Contract │ Critical https://kaiascan.io/address/0xF31CE581A8440f0f4850eDEb343a28372572a088 Copy Bridge │ Smart Contract │ Critical Show all targets Focus Area IN SCOPE VULNERABILITIES: WEB 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 IN SCOPE VULNERABILITIES: Smart Contracts We are looking for evidence and reasons for incorrect behavior of the smart contract, which could cause unintended functionality: Stealing or loss of funds Unauthorized transaction Transaction manipulation Attacks on logic (behavior of the code is different from the business description) Reentrancy Reordering Over and underflows Signature/Nonce manipulation Price manipulation Balance manipulation OUT OF SCOPE VULNERABILITIES: Smart Contracts Theoretical vulnerabilities without any proof or demonstration Old compiler version The compiler version is not locked Vulnerabilities in imported contracts Code style guide violations Redundant code Gas optimizations Best practice issues Vulnerabilities that can be exploited through front-run attacks only 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 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 AI-generated reports without runable PoC are not accepted under this program. POC's are required to execute on the deployed L1 contracts in testnet 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 05 Feb 2026 Published date 05 Feb 2026 Last updated 29 Sep 2026 Range of bounty $100 - $10,000 Severity Critical $5,000 - $10,000 High $800 - $5,000 Medium $200 - $800 Low $100 - $200 DEX Web smart contract Solidity @IamSalted KYC Verified 1 @H1xploit KYC Verified 2 @cyberarmy101 KYC Verified 3 @somveer Verified 4 @silenthere KYC Verified 5 Response type Business days First Response 3d Triage Time 7d Reward Time 3d Resolution Time 14d