CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
Aiden Labs logo
Aiden Labs
AI
Marketplace
NFT
Max Payout
$1,500
Project Overview

Aidenlabs.ai is an AI-powered agent that enables users to access popular AI tools—such as ChatGPT, Claude, Gemini, and Deepseek—directly through chat applications like Telegram. Offering a unified platform, Aidenlabs.ai allows users to generate images, create videos, and perform research seamlessly under a single subscription, enhancing productivity and ease of use.

Rewards by Severity

Program Overview Aiden Labs maintains a formal bug bounty program to identify and mitigate vulnerabilities across its smart contracts and supporting infrastructure. This initiative encourages ethical hackers and security researchers to contribute to the security and resilience of the Aiden Labs ecosystem by reporting issues that could impact its users or protocol.

Reward Structure All submissions are evaluated using a 4-tier severity model, with reward levels determined by the criticality of the vulnerability and the asset or system affected. Higher-tier rewards are assigned to issues that carry greater financial, operational, or reputational risk. Final reward amounts are determined through internal review by the Aiden Labs security team.

Submission Requirements To be eligible for a reward, reports must include a complete and functional proof of concept (PoC) along with detailed reproduction steps. The submission must clearly demonstrate the vulnerability's impact on an in-scope component. Reports that rely solely on theoretical analysis or written descriptions without executable code will not qualify.

Payouts Bounties are denominated and paid in USD, processed directly by the Aiden Labs team after successful validation of the report and completion of KYC requirements.

Smart Contract
The bounty will be paid out in USD
Assets In-Scope
Target
Severity
Name
https://github.com/Aiden-Labs/aiden-token-contract
Smart Contract
ADN/USDT
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 project funds other than unclaimed rewards
Direct theft of user funds other than unclaimed rewards
Permanent freezing of funds
Unauthorized mint/burn/transfer of crypto assets
Bad randomness leading to predictable results with serious financial impact
Governance voting result manipulation
Protocol insolvency
Major
Issues leading to temporary freezing of funds for a limited amount of time
Theft or permanent freezing of unclaimed yield and rewards
Temporary denial of services
Broken access control leads to high security risks
Medium
Unexpected logic executions (doesn’t lose value)
Smart contract unable to operate due to lack of funds or misconfiguration
Griefing attacks that can damage users or the protocol without profiting the attacker
Block stuffing for profit
Low
Important gas optimizations
Smart contract functionality significantly differs from how it is described in its official documentation
Smart contract fails to deliver promised returns - but doesn’t lose value
Missing events for functions that change critical parameters
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)
Not following best practices with no security risk
Sybil attacks
Centralization risks
Issues with no security or financial impact
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 Scope1
Live SinceFeb 26, 2025
Last Updated2mo 21d ago
Funds Reserved$3,000
Max Payout$1,500
Skynet Score
86.24
A
KYC
Required
PoC
Required
View on Skynet