Hibachi
Hibachi is a DeFi trading platform built for professionals, secured by zk math, and powered by Celestia, Risc Zero and Hashflow. For more information about Hibachi, please visit https://hibachi.xyz/.
Celestia
Defi
DEX
Maximum Bounty
$20,000Live Since
08 January 2025Last Updated
08 April 2025PoC Required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Severity
Critical
Title
Execute arbitrary system commands
Severity
Critical
Title
Retrieve sensitive data/files from a running server, such as:
- /etc/shadow
- database passwords
- blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)
Severity
Critical
Title
Taking down the application/website
Severity
Critical
Title
Taking and/modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as:
- Changing registration information
- Commenting
- Voting
- Making trades
- Withdrawals, etc.
Severity
Critical
Title
Subdomain takeover with already-connected wallet interaction
Severity
Critical
Title
Direct theft of user funds
Severity
Critical
Title
Malicious interactions with an already-connected wallet, such as:
- Modifying transaction arguments or parameters
- Substituting contract addresses
- Submitting malicious transactions
Severity
Critical
Title
Injection of malicious HTML or XSS through metadata
Severity
High
Title
Injecting/modifying the static content on the target application without JavaScript (persistent), such as:
- HTML injection without JavaScript
- Replacing existing text with arbitrary text
- Arbitrary file uploads, etc.
Severity
High
Title
Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as:
- Password of the victim etc.
Severity
High
Title
Improperly disclosing confidential user information, such as:
- Email address
- Phone number
- Physical address, etc.
Severity
High
Title
Subdomain takeover without already-connected wallet interaction
Out of scope
Program's Out of Scope information
- Unauthorized Access & Exploited Attacks
- Attacks already exploited by the reporter, causing real-world damage.
- Vulnerabilities requiring access to leaked credentials, API keys, or secrets, unless proven to be actively used in production.
- Exploits requiring privileged access (e.g., governance, strategist roles), except when the contract is explicitly designed to have no privileged access to affected functions.
- Attacks requiring access to internal test files, configuration files, or non-production environments, unless explicitly stated as in-scope.
- Attacks requiring physical access to devices, internal systems, or restricted networks.
- Third-Party & Environmental Limitations
- Issues in third-party services, infrastructure, or dependencies not owned or managed by Hibachi.
- Bugs related to outdated software versions beyond Hibachi's control (e.g., unsupported browsers).
- Attacks relying on the depegging of external stablecoins unless directly caused by a flaw in Hibachi's code.
- Reflected plain text injection (e.g., URL parameters, paths) without proof of real-world impact.
- Note: This does not exclude reflected HTML injection (with or without JavaScript) or persistent plain text injection.
- Any vulnerability requiring browser bugs for exploitation (e.g., CSP bypass).
- Server-side non-confidential information disclosure (e.g., IPs, server names, most stack traces).
- SPF/DMARC misconfigured records without security impact.
- Social Engineering & User Manipulation
- Phishing, social engineering, or coercion of Hibachi employees, partners, or users.
- CSRF vulnerabilities without state-modifying impact (e.g., logout CSRF).
- Automated testing of services generating excessive traffic (e.g., brute force, spam).
- Automated Attacks & Service Disruptions
- Denial of Service (DoS), brute force, or rate-limiting bypass attacks.
- Captcha bypass using OCR without impact demonstration.
- DDoS-only attacks with no security relevance.
- Enumeration of user existence (e.g., checking if an email is registered).
- Theoretical & Non-Exploitable Vulnerabilities
- Theoretical vulnerabilities without a working proof-of-concept (PoC).
- Issues requiring in-app user actions that are not part of normal workflows.
- Impacts requiring access to a victim’s local network (e.g., ARP spoofing, MITM).
- Lack of SSL/TLS best practices without proven exploitation.
- Leaked non-sensitive API keys (e.g., Etherscan, Infura, Alchemy).
- Automated scanner reports without impact demonstration.
- Missing HTTP headers or cookie flags (e.g., httponly, X-FRAME-OPTIONS) unless leading to an exploitable vulnerability.
- UX/UI-related bugs that do not materially impact security.
- Non-future-proof NFT rendering vulnerabilities.
Default Out of Scope and rules
Web & App specific
- Theoretical impacts without any proof or demonstration
- Impacts involving attacks requiring physical access to the victim device
- Impacts involving attacks requiring access to the local network of the victim
- Reflected plain text injection (e.g. url parameters, path, etc.)
- This does not exclude reflected HTML injection with or without JavaScript
- This does not exclude persistent plain text injection
- Any impacts involving self-XSS
- Captcha bypass using OCR without impact demonstration
- CSRF with no state modifying security impact (e.g. logout CSRF)
- Impacts related to missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
- Server-side non-confidential information disclosure, such as IPs, server names, and most stack traces
- Impacts causing only the enumeration or confirmation of the existence of users or tenants
- Impacts caused by vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
- Lack of SSL/TLS best practices
- Impacts that only require DDoS
- UX and UI impacts that do not materially disrupt use of the platform
- Impacts primarily caused by browser/plugin defects
- Leakage of non sensitive API keys (e.g. Etherscan, Infura, Alchemy, etc.)
- Any vulnerability exploit requiring browser bugs for exploitation (e.g. CSP bypass)
- SPF/DMARC misconfigured records)
- Missing HTTP Headers without demonstrated impact
- Automated scanner reports without demonstrated impact
- UI/UX best practice recommendations
- Non-future-proof NFT rendering
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers