Only the latest release is in scope for Blockchain/DLT and Web/App assets. You can access the latest release for a repository by adding "releases/latest" to the end of a repository's URL.

Never run tests on Hathor's production environments such as the mainnet. If you believe your attack would only work in our production environment, get in touch with us at security@hathor.network. 

All config and test files are considered as out-of-scope of this bug bounty program. 

Hathor-core/hathor/wallet is out-of-scope.  [https://github.com/HathorNetwork/hathor-core/tree/master/hathor/wallet](https://github.com/HathorNetwork/hathor-core/tree/master/hathor/wallet)

All code of Hathor Network can be found at [https://github.com/HathorNetwork.](https://github.com/HathorNetwork) However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Documentation and instruction for PoC can be found here:
- [https://hathor.gitbook.io/hathor/](https://hathor.gitbook.io/hathor/)
- [https://github.com/HathorNetwork/rfcs/blob/master/text/0033-private-network-guide.md](https://github.com/HathorNetwork/rfcs/blob/master/text/0033-private-network-guide.md)


Hathor is a digital platform for financial transactions and contracts with a unique combination of high scalability and high decentralization. It creates the perfect environment for multiple use cases where scale, efficiency, long-term security, and censorship-resistance through network distribution combined are needed or can drastically cut current costs and bureaucracy.

Network not being able to confirm new transactions (Total network shutdown)

Unintended permanent chain split requiring hard fork (Network partition requiring hard fork)

Direct loss of funds

Permanent freezing of funds (fix requires hardfork)

Creation of tokens, including HTR, without following blockchain and consensus rules

Execute arbitrary system commands

Direct theft of user funds

Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, and submitting malicious transactions

Direct theft of user NFTs

Unintended chain split (Network partition)

Transient consensus failures

High compute consumption by validator/mining nodes

Attacks against thin clients

DoS of greater than 30% of validator or miner nodes and does not shut down the network

DoS of greater than 10% but less than 30% of validator or miner nodes and does not shut down the network

Changing details of other users (including modifying browser local storage) without already-connected wallet interaction and with significant user interaction such as iframing leading to modifying the backend/browser state (demonstrate impact with PoC)

Rewards are distributed according to the impact of the vulnerability based on the  [Immunefi Vulnerability Severity Classification System V2.2.](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2/) This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported. 

All Blockchain/DLT and Web/App bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required. Bug reports are required to include a runnable PoC in order to prove impact. Exceptions may be made in cases where the vulnerability is objectively evident from simply mentioning the vulnerability and where it exists. However, the bug reporter may be required to provide a PoC at any point in time.

Hathor Labs requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is a government ID and proof of address.

Unlike other bug bounty programs on Immunefi, all bug report submissions, including associated vulnerabilities, become the exclusive property of Hathor Labs. By making a submission to this program and in consideration for a bounty, the bug submitter conveys all ownership rights, titles, and interests in the bug report to Hathor Labs. Thus, the final decision on whether a postmortem will be written is at the sole discretion of Hathor Labs.

Payouts are handled by the __Hathor Labs__ team directly and are denominated in USD. However, payouts are done in __HTR__.


Hathor Network

Resources & Documentation