CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
Bad Idea logo
Bad Idea
AI
DeFi
DAO
Max Payout
$5,000
Project Overview

Bad Idea AI ($BAD) is a decentralized experiment blending Blockchain, AI, and DAO governance into a bold, meme-driven initiative. Exploring the dual nature of AI—from personal assistants to autonomous vehicles—$BAD empowers both AI and its community to shape the future, embracing risk and uncertainty. Positioned as humanity’s “Hail Mary” pass, $BAD is a provocative attempt to navigate AI’s promise and peril through decentralized collaboration and innovation.

Rewards by Severity

Program Overview The Bad Idea Bug Bounty Program is a proactive security initiative designed to engage ethical hackers, developers, and security researchers in strengthening the Bad Idea ecosystem. Participants are encouraged to identify and responsibly disclose vulnerabilities across smart contracts, dApps, and supporting infrastructure, helping to ensure the safety and reliability of the network.

Reward Structure All submissions are reviewed under a 4-tier severity model, with rewards based on the criticality and impact of the discovered issue. For critical smart contract vulnerabilities, rewards are capped at 10% of the economic damage, considering both the value of funds at risk and reputational impact. High-severity vulnerabilities may be rewarded up to 100% of the affected value, based on the state of the system at the time of report submission.

Submission Requirements To be eligible for rewards, bug reports must include a working proof of concept (PoC) and clear steps to reproduce the vulnerability. Reports must demonstrate a tangible impact on an in-scope asset. Theoretical issues or submissions without executable code will not qualify.

Payouts All bounty rewards are denominated and paid in USDT, and distributed by the Bad Idea team after successful validation.

Smart Contract
The bounty will be paid out in USDT
Assets In-Scope
Target
Severity
Name
https://github.com/MrLightspeed/Bad-Idea-AI/blob/main/Badideaai.sol
Smart Contract
Bad Idea AI Smart Contract
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
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
Low
Smart contract functionality significantly differs from how it is described in its official documentation
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
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 SinceJan 1, 2025
Last Updated2mo 21d ago
Funds Reserved$5,000
Max Payout$5,000
Skynet Score
79.87
BBB
KYC
Required
PoC
Required
View on Skynet