Decentralized Security, Community-Powered Recon

Bounty Overview Rewards by Severity Assets in Scope In-scope Vulnerabilities Out-of-scope Vulnerabilities Program Rules FAQs

Particle Network

Web3

Infrastructure

Wallet

Max Payout

$5,000

Project Overview

Particle Network is a leading infrastructure provider offering end-to-end solutions for Web3 application development. Its core products include a secure Authentication and Wallet-as-a-Service middleware powered by Multi-Party Computation (MPC), enabling seamless user onboarding and wallet integration. In addition, Particle provides a one-stop NFT toolkit and robust Node RPC & Data API services, streamlining the development and deployment of decentralized applications across ecosystems.

Rewards by Severity

Program Overview Particle Network operates a structured bug bounty program to strengthen the security and reliability of its full-stack Web3 infrastructure. As a data-driven and composable development platform, Particle Network empowers decentralized application builders through a suite of services including secure authentication, wallet-as-a-service middleware powered by Multi-Party Computation (MPC), a one-stop NFT solution, and Node RPC & Data API services. This program supports the project’s broader vision to accelerate global adoption of the cryptoverse through responsible vulnerability disclosure.

Reward Structure All reports are assessed using a 4-tier severity model, with reward levels determined by the criticality of the vulnerability and the affected component—whether smart contracts, authentication flows, APIs, or frontend systems. High-impact issues with the potential to compromise user funds or core services will qualify for upper-tier rewards.

Submission Requirements Submissions must include a working proof of concept (PoC) that demonstrates clear impact on an in-scope target, accompanied by detailed reproduction steps. Reports consisting only of theoretical analysis or lacking code will not be considered for rewards.

Payouts Rewards are denominated in USD and paid in USDT, distributed directly by the Particle Network team upon successful report validation and KYC completion.

Application/Web

The bounty will be paid out in USDT

Assets In-Scope

Target

Severity

Name

https://wallet-debug.particle.network/

Application/Web

Particle Wallet

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.

Application/Web

Critical

System Hacked

Major

Remote code execution and code injection

SQL injection

Obtaining high-impact sensitive information from the internal system

XXE/XML injection vulnerability with high-security impact

Authentication and authorization bypass with high impact

Wormable stored XSS

Large scale account takeover

Leakage of a lot of source code

Medium

Account takeover

Stored XSS on general pages

CSRF involving core business

IDOR with medium security impact/Horizontal and Vertical Privilege Escalation

The leakage of locally-stored sensitive authentication key information

Medium impact information disclose

Low

General information leakage - such as web path traversal - system path traversal - directory browsing etc

Reflected XSS - DOM XSS and Flash-based XSS

SMS bombs - mail bombs (each system only accepts one type of this vulnerability)

No return value and no in-depth utilization of successful SSRF

Other vulnerabilities with low-security impact

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.

Application/Web

Clickjacking

Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions - Login/Logout CSRF

CORS misconfiguration with no security 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 SinceJun 7, 2023

Last Updated2mo 20d ago

Funds Reserved$20,000

Max Payout$5,000

Skynet Score

90.71

KYC

Required

PoC

Required

View on Skynet