Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Folks Finance

Bug bounty on Immunefi folks.finance

Accepting reports KYC to get paid Algorand Defi Lending
Go to program Website
Top reward
$100,000
Top severity paid
Critical
Assets in scope
21
Public CVEs
0
Last change

At a glance

What to know before you start testing.

Pays up to $100,000
for critical bugs, from $1,000.
Report on Immunefi
Submit through the program page.
Paid by USDC
Proof of identity needed to get paid.
Publish after a fix
Coordinate the timing with the company.

Rewards

What Immunefi lists as the payout for each severity.

Severity Reward
Critical $100,000 10% of funds at risk · from $25,000
High $50,000 from $5,000
Medium $2,500
Low $1,000

Scope

21 assets you may test.

Domains 21

  • lora.algokit.io/mainnet/application/1040271396
  • lora.algokit.io/mainnet/application/1134695678
  • lora.algokit.io/mainnet/application/1258515734
  • lora.algokit.io/mainnet/application/1258524099
  • lora.algokit.io/mainnet/application/2611131944
  • lora.algokit.io/mainnet/application/3184317016
  • lora.algokit.io/mainnet/application/3184324594
  • lora.algokit.io/mainnet/application/3184325123
  • lora.algokit.io/mainnet/application/3184333108
  • lora.algokit.io/mainnet/application/3343137163
  • lora.algokit.io/mainnet/application/3514794123
  • lora.algokit.io/mainnet/application/3514795114
  • lora.algokit.io/mainnet/application/971333964
  • lora.algokit.io/mainnet/application/971350278
  • lora.algokit.io/mainnet/application/971353536
  • lora.algokit.io/mainnet/application/971368268
  • lora.algokit.io/mainnet/application/971372237
  • lora.algokit.io/mainnet/application/971373361
  • lora.algokit.io/mainnet/application/971373611
  • lora.algokit.io/mainnet/application/971388781
  • lora.algokit.io/mainnet/application/971389489

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Folks Finance (via Immunefi)'s policy. "We" in these lines means the program, not this site.

While testing

  • Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
  • 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 that are executed against project assets
  • Automated testing of services that generates significant amounts of traffic
  • Public disclosure of an unpatched vulnerability in an embargoed bounty

Not accepted

  • All vulnerabilities marked in the following Github repository https://github.com/Folks-Finance/audits are ineligible for a reward
  • Bug reports related solely to external incentives distributed on top of the protocol are downgraded in severity by one level.
  • Bug reports covering previously-discovered bugs are not eligible for any reward through the bug bounty program.

Summarised with AI from the program policy on Immunefi, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 36 minutes ago.

  1. Cut

    Top reward $200,000 to $100,000.

Before we tracked it

Scope and reward changes recorded before this page started tracking it.

  1. Rules updated

    The program rules were edited

  2. Reward terms

    The reward table or payout terms were edited

  3. Scope added

    https://lora.algokit.io/mainnet/application/1134695678

  4. Scope removed

    https://docs.folks.finance/developer/contracts

  5. Rules updated

    The program rules were edited

  6. Reward terms

    The reward table or payout terms were edited

  7. Reward cut

    Maximum $200,000 → $100,000

  8. Scope removed

    https://docs.xapp.folks.finance/developers/contracts

  9. Rules updated

    Added: “…eing known before escalation of the bug report via Immunefi.”

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.

Original policy

Copied from immunefi.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Back to Explore Folks Finance | Folks Finance is a community-driven DeFi protocol offering a variety of tools for digital asset management Algorand Defi Lending Python Maximum Bounty $100,000 Live Since 31 March 2022 Last Updated 08 October 2026 Runnable PoC Required KYC required Submit a Bug Information Scope Resources Rewards Folks Finance provides rewards in USDC on Ethereum , denominated in USD. Rewards by Threat Level Smart Contract Critical Max: $100,000 Min: $25,000 Primacy of Rules High Max: $50,000 Min: $5,000 Primacy of Rules Medium Flat: $2,500 Primacy of Rules Low Flat: $1,000 Primacy of Rules Critical Reward Calculation Mainnet assets: Reward amount is 10 % of the funds directly affected up to a maximum of: $100,000 Minimum reward to discourage security researchers from withholding a bug report: $25,000 Rewards Body Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2 . This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported. Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required. High and Critical smart contract vulnerabilities are capped at 10% of economic damage, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of USD 50 000 for Critical and USD 10 000 for High. All vulnerabilities marked in the following Github repository https://github.com/Folks-Finance/audits are ineligible for a reward Bug reports related solely to external incentives distributed on top of the protocol are downgraded in severity by one level. Bug reports covering previously-discovered bugs are not eligible for any reward through the bug bounty program. If a bug report covers a known issue, it may be rejected together with proof of the issue being known before escalation of the bug report via Immunefi. KYC shall be completed for bug bounty hunters submitting a vulnerability report and requesting a reward for Critical and High Smart Contracts vulnerabilities. The basic information needed is full name, residential address, and passport details (DOB, issuing country and passport number). Based on the basic information submitted, Folks Finance team may request further information at its sole discretion for compliance with applicable Laws. Additionally, all levels of bug bounty hunters submitting a vulnerability report and requesting a reward need to submit certification that (i) they are not acting, directly or indirectly, for or on behalf of any person, group entity, or nation named by any Executive Order or the United States Treasury Department as a terrorist, “Specially Designated National and Blocked Person,” or other banned or blocked person, entity, nation, or transaction pursuant to any law, order, rule or regulation that is enforced or administered by the Office of Foreign Assets Control; and (ii) they are not engaging in, instigating or facilitating this transaction, directly or indirectly, on behalf of any such person, group, entity, or nation. They also need to submit an attestation that all information provided is true, correct, up-to-date and not misleading. The collection of this information will be done by the Folks Finance team. Payouts are handled by the Folks Finance team directly and are denominated in USD. However, payouts are done in USDC . View impacts in scope Program Overview Folks Finance is a community-driven DeFi protocol offering a variety of tools for digital asset management For more information about Folks Finance, please visit https://folks.finance/ . This bounty program will expire on 31.12.2026 Known Issues Category Description / Link Last Updated At Smart Contract │ An attacker sends some fAsset, whose pool's collateral cap is zero, to a loan such that it prevents the loan from being closed out. Other similar examples such as when an escrow has opted into a different asset prior to being used 1 January 2023 Category Smart Contract Description / Link An attacker sends some fAsset, whose pool's collateral cap is zero, to a loan such that it prevents the loan from being closed out. Other similar examples such as when an escrow has opted into a different asset prior to being used Last Updated At 1 January 2023 KYC required The submission of KYC information is a requirement for payout processing. Participants must adhere to the Eligibility Criteria. Proof of Concept Proof of concept is always required for all severities. Responsible Publication Category 3: Approval Required Prohibited Activities Default prohibited activities Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet 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 that are executed against project assets Automated testing of services that generates significant amounts of traffic Public disclosure of an unpatched vulnerability in an embargoed bounty Any other actions prohibited by the Immunefi Rules Feasibility Limitations The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity. Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report. Chain Rollbacks Pre-Impact Bug Monitoring Attack Investment Amount Attacks With A Financial Risk To The Attacker When Is An Impactful Attack Downgraded To Griefing? Submit a Bug Total Assets in Scope 21