Jungle Smart Contract

Triaged by HackenProof

Jungle is a peer-to-peer NFT marketplace for digital goods, art, collectibles, and other virtual assets backed on the blockchain. JungleNFT allows anyone to buy and sell items through smart contracts and aims to make the world of non-fungible tokens accessible for every type of buyer, from crypto novice to seasoned collector.

In Scope

Target Type Severity Reward

ETH WyvernProxyRegistry

Smart Contract Critical Bounty

ETH WyvernTokenTransferProxy

Smart Contract Critical Bounty

ETH NFT Contract

Smart Contract Critical Bounty

ETH Exchange Contract

Smart Contract Critical Bounty

ETH Atomicizer Contract

Smart Contract Critical Bounty

ETH MerkleValidator

Smart Contract Critical Bounty

ETH JungleRelayer

Smart Contract Critical Bounty

Polygon WyvernProxyRegistry

Smart Contract Critical Bounty

Polygon WyvernTokenTransferProxy

Smart Contract Critical Bounty

Polygon NFT Contract

Smart Contract Critical Bounty

Polygon Exchange Contract

Smart Contract Critical Bounty

Polygon Atomicizer Contract

Smart Contract Critical Bounty

Polygon MerkleValidator

Smart Contract Critical Bounty

Polygon JungleRelayer

Smart Contract Critical Bounty


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


  • 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

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

Please note: 1 million bounty is possible only in next cases:

  1. Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield of over $10m.
  2. Permanent freezing of funds of over $10m dollars.
    And according to possible impact (for example all users or just a set of users) we will choose the bounty amount In all other cases the issue will be marked lower than critical

Disclosure Policy & Guidelines

  • As this is a private program, please 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

Eligibility & Coordinate We are happy to thank everyone who submits valid reports, which help us improve the security. However, only those who meet the following eligibility requirements may receive a monetary reward:

  • You must be the first vulnerability reporter.
  • 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, including
  • 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 contractors.
  • ONLY USE YOUR HackerProof ADDRESS (in case of violation, no bounty can be awarded)
  • Provide detailed but to-the-point reproduction steps