Multipli Web
By Multipli Bug bounty on HackenProof multipli.fi
- Top reward
- $2,000
- Top severity paid
- Critical
- Assets in scope
- 3
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $2,000
- for critical bugs.
- Report on HackenProof
- Submit through the program page.
- Partial safe harbor
- Some legal protection; read the terms.
- 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 |
|
$2,000 |
- Response
-
Within 3 days
First Response 3d
- Safe harbor
-
Partial
Don’t break any law and stay in the defined scope
- Hall of fame
-
Yes
We are happy to thank everyone who submits valid reports which help us improve the security.
Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
3 assets you may test, 3 excluded.
Web 2
- https://app.multipli.fi
- https://multipli.fi
Wildcard domains 1
- *.multipli.fi
Out of scope (3)
- blog.multipli.fi
- status.multipli.fi
- testnet.multipli.fi
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Multipli Web (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
-
You must be at least 18 years old.
-
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
Not accepted
-
Vulnerabilities in third-party applications
-
Assets that do not belong to the company
-
Clickjacking on pages with no sensitive actions
-
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
-
CORS related issues unless you can exfiltrate data.
-
Open redirect - unless an additional security impact can be demonstrated
-
Session fixation
-
User account enumeration
-
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 34 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 Multipli Web: Program info Multipli Web Company: Multipli Scope Review: 294906 Submissions: 73 Total rewards: $100 Reputation 150 points required PoC Required Program is: active now Live Submit report Program info Hackers 40 Reports 0 Multipli is a Zk based yield protocol specifically designed for making yield on traditionally non-yield bearing assets (XAUT (tokenised Gold), BTC, etc) and also boosting yield bearing capacity of any asset by 4-12%. All Scope Focus Area Program Rules Eligibility and Coordinated Disclosure Disclosure Guidelines Scope Search targets In scope Target │ Type │ Severity https://multipli.fi Copy Web │ None https://app.multipli.fi Copy Web │ None *.multipli.fi Copy Web │ None Out of scope Out of scope Target │ Type │ Severity blog.multipli.fi Copy Web │ None status.multipli.fi Copy Web │ None testnet.multipli.fi Copy Web │ None 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 Clickjacking on pages with no sensitive actions 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 CORS related issues unless you can exfiltrate data. 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 redirect - unless an additional security impact can be demonstrated 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 Leakage of non sensitive API keys (e.g. Etherscan, Infura, Alchemy, etc.) Any vulnerability exploit requiring browser bugs for exploitation (e.g. CSP bypass) UI/UX best practice recommendations Automated scanner reports without demonstrated impact Comma Separated Values (CSV) injection without demonstrating a vulnerability. Response manipulations without demonstration of system state change Program Rules Avoid using web application scanners for automatic vulnerability searching which generates massive traffic You must be at least 18 years old. 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. 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 24 Feb 2026 Published date 24 Feb 2026 Last updated 12 Aug 2026 Range of bounty $0 - $2,000 Severity Critical $1,000 - $2,000 High $800 - $1,000 Medium $300 - $800 Low $0 - $300 Staking Web @itsdarktoday KYC Verified 1 @ertugrul Verified 2 @Sabby Verified 3 @0xkujen KYC Verified 4 @theFirstElder KYC Verified 5 Response type Business days First Response 3d Triage Time 3d Reward Time 3d Resolution Time 14d