DeFine

The core of DeFine is SOCIAL. DeFine is the NFT social platform for all creators including artists, musicians, inuencers, and gamers. The platform facilitates all social interaction, engagement and communication for creators and their fanbase through marketplace features that utilize digital assets like NFTs, social/fan tokens, and real assets on the blockchain. Owners of social/fan tokens will have many benefits including special access to the creators’ NFTs, merchandise, content, etc. while being part of a private community. It is also the social platform for all participants in the digital world where they can identify and interact with each other through their NFT social profiles which are based on their contribution and achievements in the digital world.

Ultimately, the DeFine will serve as a social platform for creators and users to define how to engage with each other and build communities in the digital world.

For more information about DeFine, please visit https://define.one/.

This bug bounty program is focused on their smart contracts and app and is focused on preventing:

• Thefts and freezing of governance funds (including tokens staked for proposals)
• Unintended buying or selling behavior of marketplace smart contract (e.g. acquiring NFTs on sale for free, or failure to deliver the asset even after the payment has been made)
• Theft or freezing of staked asset
• Unintended exploits using Badge multiplier benefits
• Theft or freezing of funds regarding Pad claims

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

All web/app bug reports must come with a PoC in order to be considered for a reward. Critical/High severity smart contract bug reports must come with a PoC and a suggestion for a fix in order to be considered for a reward. Medium severity smart contract bug reports must come with a PoC in order to be considered for a reward.

DeFine requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is Name, Email, Nationality and Contact Number.

Payouts are handled by the DeFine team directly and are denominated in USD. Payouts are done in USDT.

All smart contracts of DeFine can be found at https://github.com/defineart. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

Impacts in Scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.

Smart Contracts/Blockchain

• Thefts and freezing of governance funds (including tokens staked for proposals)
• Unintended buying or selling behavior of marketplace smart contract (e.g. acquiring NFTs on sale for free, or failure to deliver the asset even after the payment has been made)
• Theft or freezing of staked asset
• Unintended exploits using Badge multiplier benefits
• Theft or freezing of funds regarding Pad claims

Web/App

• Redirected funds by address modification
• Site goes down
• Accessing sensitive pages without authorization

We are especially interested in receiving and rewarding vulnerabilities of the following types:

Smart Contracts and Blockchain

• Re-entrancy
• Logic errors
  • including user authentication errors
• Solidity/EVM details not considered
  • including integer over-/under-flow
  • including rounding errors
  • including unhandled exceptions
• Trusting trust/dependency vulnerabilities
  • including composability vulnerabilities
• Oracle failure/manipulation
• Novel governance attacks
• Economic/financial attacks
  • including flash loan attacks
• Congestion and scalability
  • including running out of gas
  • including block stuffing
  • including susceptibility to frontrunning
• Consensus failures
• Cryptography problems
  • Signature malleability
  • Susceptibility to replay attacks
  • Weak randomness
  • Weak encryption
• Susceptibility to block timestamp manipulation
• Missing access controls / unprotected internal or debugging interfaces

Websites and Apps

• Remote Code Execution
• Trusting trust/dependency vulnerabilities
• Vertical Privilege Escalation
• XML External Entities Injection
• SQL Injection
• LFI/RFI
• Horizontal Privilege Escalation
• Stored XSS
• Reflective XSS with impact
• CSRF with impact
• Direct object reference
• Internal SSRF
• Session fixation
• Insecure Deserialization
• DOM XSS
• SSL misconfigurations
• SSL/TLS issues (weak crypto, improper setup)
• URL redirect
• Clickjacking (must be accompanied with PoC)
• Misleading Unicode text (e.g. using right to left override characters)

The following vulnerabilities are excluded from the rewards for this bug bounty program:

• Attacks that the reporter has already exploited themselves, leading to damage
• Attacks requiring access to leaked keys/credentials
• Attacks requiring access to privileged addresses (governance, strategist)

Smart Contracts and Blockchain

• Incorrect data supplied by third party oracles
  • Not to exclude oracle manipulation/flash loan attacks
• Basic economic governance attacks (e.g. 51% attack)
• Lack of liquidity
• Best practice critiques
• Sybil attacks

Websites and Apps

• Theoretical vulnerabilities without any proof or demonstration
• Content spoofing / Text injection issues
• Self-XSS
• Captcha bypass using OCR
• CSRF with no security impact (logout CSRF, change language, etc.)
• Missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”)
• Server-side information disclosure such as IPs, server names, and most stack traces
• Vulnerabilities used to enumerate or confirm the existence of users or tenants
• Vulnerabilities requiring unlikely user actions
• URL Redirects (unless combined with another vulnerability to produce a more severe vulnerability)
• Lack of SSL/TLS best practices
• DDoS vulnerabilities
• Attacks requiring privileged access from within the organization
• Feature requests
• Best practices

The following activities are prohibited by this bug bounty program:

• Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
• Any testing with pricing oracles or third party smart contracts
• Attempting phishing or other social engineering attacks against our employees and/or customers
• Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
• Any denial of service attacks
• Automated testing of services that generates significant amounts of traffic
• Public disclosure of an unpatched vulnerability in an embargoed bounty