Forta Token Proxy and corresponding implementation

Access Proxy and corresponding implementation

Router Proxy and corresponding implementation

Agents (Detection Bots) Proxy and corresponding implementation

Scanners Proxy and corresponding implementation

Dispatch Proxy and corresponding implementation

Forta Token (Bridged) and corresponding implementation

Staking Proxy and corresponding implementation

Staking Parameters Proxy and corresponding implementation

Scanner Node Version Proxy and corresponding implementation

Nodes/ detection bots deployed on the forta network as listed on the Forta App.

All smart contracts of Forta can be found at [https://github.com/forta-network/forta-contracts](https://github.com/forta-network/forta-contracts). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Though only the proxy contracts are listed as in-scope, current implementation and any further updates to the implementation contracts are considered in scope. When reporting a bug, please make sure to select the relevant proxy smart contract as the target. 

If an impact can be caused to any other asset managed by Forta that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project. This applies to only Critical and High impacts. 

Exceptions: The are specific bugs not eligible for a Bounty, as they have already been identified and fixes are in progress.
  - A protocol vulnerability where a Scan Pool Owner is able to withdraw their stake without disabling their scan nodes if there is enough Delegated Stake in the Scan Pool.  The intention was to always require Owners to have a minimum stake level so that they always have a direct incentive to avoid malicious activity.  
The Delegator’s stake should be unallocated when owner’s stake is withdrawn Add check to disableScanner before decrementing the amount of enabled scanners in a scanner pool Bypassing of max allocation by staking very large amount (needs to be further clarified) 
  - Issue in setting up a new pool with large stake setDelegationParams function in RewardsDistributor not setting delegationParamsEpochDelay 
  - Setting a pool's fee to 0 causes the pool's fee to actually become 100% because the contract assumes that trying to set it to 0 means there is no fee set, and thus defaults to 100%. 
  - Signing up for subscriptions repeatedly and hitting verify email a lot which sends a lot of emails
  - Bots that emit too many alerts
  - An owner can emit infinite bots, and too many is too many - but staking mitigates that and we can slash + take other actions
  - Nodes that handle their nodes insecurely - putting them on the public internet  / exposing sensitive credentials within network endpoints
  - Someone with a private key of an enabled&staked scan node can submit fake alerts for any bot 

For more documentation, please refer to [https://docs.forta.network/en/latest/](https://docs.forta.network/en/latest/).  

Forta is a decentralized monitoring network to detect threats and anomalies on DeFi, NFT, governance, bridges and other Web3 systems in real-time.

Service wide disruption that impacts the ability of Forta to scan and analyze transactions. 10%+ of transaction of permanent scan failures

Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Protocol insolvency

Execute arbitrary system commands

Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys(this does not include non-sensitive environment variables, open source code, or usernames)

Taking down the application

Taking state-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.

Subdomain takeover with already-connected wallet interaction

Direct theft of user funds

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

Service wide disruption that impacts the ability of Forta to scan and analyze transactions. 5%+ of transaction of permanent scan failures

Theft of unclaimed yield

Temporary freezing of funds for a minimum period of 7 days

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.

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 email or password of the victim, etc.

Improperly disclosing confidential user information such as email address, phone number, physical address, etc.

Subdomain takeover without already-connected wallet interaction

Disruption of bot notifications (multiple channels)

Reduction of capacity of the network by 50%

Inability to deploy new detection bots or reassign detection bots

Inability to register new scan nodes

Deregistering nodes/ detection bots

Reassigning nodes/ detection bots

Changing non-sensitive details of other users (including modifying browser local storage) w/o already-connected wallet interaction & with up to one click of user interaction, such as changing the first/last name of user, or enabling/disabling notifications

Injecting/modifying the static content on the target application without Javascript (Reflected) such as reflected HTML injection or loading external site data

Redirecting users to malicious websites (Open Redirect)

Reduction of capacity of the network by 10%

Inability to deploy new detection bots or reassign detection bots; work around exist (e.g. deployment vis CLI if dapp deployment is disrupted)

Inability to register new scan nodes; work around exists

Inability to register nodes/ detection bots

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

Any impact involving a publicly released CVE without a working PoC

Taking over broken or expired outgoing links such as social media handles, etc.

Temporarily disabling user to access target site, such as locking up the victim from login, cookie bombing, etc.

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 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. All Blockchain/DLT and Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.

All rewards for the Forta bug bounty program are scaled based on an internally established team criteria, taking into account the exploitability of the bug, the impact it causes, and the likelihood of the vulnerability presenting itself, which is especially factored in with bug reports requiring multiple conditions to be met that are currently not in-place. Rewards will be provided at the determined fair value by the team depending on these conditions, assuming that the bug report is in-scope of the bug bounty program.

The following vulnerabilities are not eligible for a reward:

  - Frontrunning protection for Agent (Bot) registrations are disabled

The rewards for the Forta Network section, labeled as Blockchain/DLT in this bug bounty program, are only for the Forta Network assets.

Forta requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is a copy of ID with name/address and country of residence. The collection of this information will be done by the Forta team.

Payouts are handled by the __Forta__ team directly and are denominated in USD. However, payouts are done in __FORT__.

Forta Network

Resources & Documentation