CertiK LogoCertiK Logo
aarna protocol logo
aarna protocol
DeFi
Store Of Value
AI
Max Payout
$2,500
Project Overview

aarnâ is an advanced DeFi asset management platform that combines AI and blockchain to optimize users’ digital asset lifecycles. Utilizing deep learning models trained on blockchain data, technical indicators, and social sentiment, aarnâ identifies alpha opportunities and tokenizes them into structured products called âfi vaults. Powered by a system of eight smart contracts, these vaults automate complex DeFi strategies, making them accessible through stablecoin deployment.

Rewards by Severity

Program Overview The aarnâ Bug Bounty Program is designed to uphold the highest standards of security within its ecosystem by proactively identifying and addressing vulnerabilities. The program encourages developers, ethical hackers, and security experts to responsibly disclose flaws in the aarnâ infrastructure, supporting a more resilient and trustworthy user environment.

Reward Structure All submissions are evaluated using a 4-level severity model, with rewards varying based on the criticality of the issue and the affected system components. Higher rewards are granted for issues with significant risk to user funds, platform stability, or core operations. Final bounty amounts are determined by the aarnâ team upon validation.

Submission Requirements To be eligible for a reward, all reports must include a working proof of concept (PoC) and clear reproduction steps demonstrating how the vulnerability affects in-scope systems. Submissions without code, or relying solely on explanation or hypothetical scenarios, will not qualify for rewards.

Payouts All bounty rewards are split evenly—50% in USDC and 50% in $AARNA tokens (to be released)—and issued by the aarnâ team upon successful report validation and completion of KYC.

Smart Contract
Web Application
The bounty will be paid out in 50% USDC / 50% AARNA
Assets In-Scope
Target
Severity
Name
Web Application
aarnâ dApp
In-Scope Vulnerabilities
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered in-scope, even if they affect something in the assets in scope table.
Smart Contract
Critical
Direct theft of any user funds - whether at-rest or in-motion - other than unclaimed yield
Freezing or shutdown of systems
Major price manipulation (>=50)
Unauthorized mint/burn/transfer of assets
Permanent denial of services
Double spending
Major
Faulty usage of proxy patterns
Access control is bypassed - including privilege escalation
Theft or permanent freezing of unclaimed yield
Medium
Users could lose funds due to rounding
Griefing (e.g. no profit motive for an attacker but damage to the users or the protocol)
Low
Non-intuitive return values
Smart contract functionality significantly differs from how it is described in its official repo
Smart contract fails to deliver promised returns - but doesn’t lose value
Missing events for functions that change critical parameters
Minor price manipulation
major gas optimization
Web Application
Critical
Smart contract fails to deliver promised returns - but doesn’t lose value
Major
Remote code execution and code injection
Obtaining high-impact sensitive information from the internal system
Authentication and authorization bypass with high impact
Large scale account takeover
Medium
Account takeover
IDOR with medium security impact/Horizontal and Vertical Privilege Escalation
The leakage of locally-stored sensitive authentication key information
Low
General information leakage - such as web path traversal - system path traversal - directory browsing etc
Out-Of-Scope Vulnerabilities
The following vulnerabilities are excluded from the rewards for this bug bounty program:
  • Vulnerabilities that have already been exploited
  • Centralization-related vulnerabilities related to: private keys, privileged addresses, governance, credentials, etc.
Smart Contract
Incorrect data supplied by third party oracles (Not to exclude oracle manipulation/flash loan attacks)
Basic economic governance attacks (e.g. 51% attack)
Best practice critiques
Sybil attacks
Centralization risks
Web Application
Email Spoofing - SPF/DMARC Records Misconfiguration
Clickjacking
Any activity that could lead to the disruption of our service (DoS)
Missing best practices in SSL/TLS configuration
Previously known vulnerable libraries without a working Proof of Concept
Issues that require unlikely user interaction
Unconfirmed reports from automated vulnerability scanners
Reports exploiting the behavior of - or vulnerabilities in - outdated browsers
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions - Login/Logout CSRF
Non-Sensitive Data Disclosure - for example server version banners
CSV/formula injection
Self-XSS with no security impact
CORS misconfiguration with no security impact
Missing HttpOnly or Secure flags on cookies
Presence of autocomplete attribute on web forms
Program Rules
  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue - the issue will not be eligible for a reward.
  • Submit one vulnerability per report - unless you need to chain vulnerabilities to provide impact.
  • When duplicates occur we only award the first report that was received (provided that it can be fully reproduced).
  • Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
  • Make a good faith effort to avoid privacy violations - destruction of data - and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
  • Do not attempt to conduct post-exploitation including modification or destruction of data - and interruption or degradation of services.
  • Do not attempt to perform brute-force attacks or denial-of-service attacks.
  • Do not attempt to target employees or customers including social engineering attacks - phishing attacks or physical attacks.
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.
  • Automated testing of services that generate significant amounts of traffic.
  • Public disclosure of an unpatched vulnerability in an embargoed bounty.
  • Social engineering (e.g. phishing, vishing, smishing) of any kind.
FAQs
How do I search for active bounties?
A: Active bounties can be viewed here [CertiK URL], and by filtering for bounties on the Security Leaderboard. Projects will post bounties along with the assets in the scope of the bounties with a corresponding bounty reward.
How do I submit a bounty?
To submit a bug report, first register an account with us https://www.certik.com/auth/signup. Once your account is created, you can log in and select “Submit Bug” for the specific bounties you're interested in. You will be prompted to fill out a webform; follow the instructions and upon successful submission, you will receive an email confirmation with a reference ID.
Who do I contact if I'm having trouble with my bug report submission?
You can reach out to bugbounty@certik.com for updates and assistance with your bug bounty submission.
I submitted my bug report. What now?
Once your bug report is submitted, CertiK will evaluate the report and contact the respective project. Depending on the criteria stated within a bug bounty, a KYC may be required. With valid bug reports, you will be contacted to begin the process of evaluating the bug with the project.
How is KYC handled?
CertiK has a team of investigative professionals that will handle any needed KYC services for bug bounty submissions requiring KYC.
Why was my bug report submission rejected?
A description of dismissal will be available for any bug bounty that is rejected.
The project is being slow responding to my bug report. What are their required response times / SLAs?
There can be multiple bug bounty submissions therefore there might be some delay in process times.
How do payouts work?
Payments for successful bug bounties will be communicated directly via the project wherein wallet information can be exchanged.
Bounty Highlights
Assets in Scope34
Live SinceAug 15, 2024
Last Updated3mo 13d ago
Funds Reserved$25,000
Max Payout$2,500
Skynet Score
87.66
AA
KYC
Required
PoC
Required