- Top reward
- $5,000
- Top severity paid
- Critical
- Assets in scope
- 18
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- Pays up to $5,000
- for critical bugs.
- Report on HackerOne
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- No public write-ups
- Keep findings private.
Rewards
What HackerOne lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
$5,000 |
| High |
|
$2,000 |
| Medium |
|
$400 |
| Low |
|
$200 |
- Safe harbor
-
Full
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you.
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
18 assets you may test, 3 excluded.
Web 17
- accounts.pixiv.net Critical
- booth.pm Critical
- coban.pixiv.net Critical
- comic-indies.pixiv.net Critical
- comic.pixiv.net Critical
- dic.pixiv.net Critical
- https://vroid.com/studio Critical
- hub.vroid.com Critical
- neoket.net Critical
- novel.pixiv.net Critical
- pastela.app Critical
- payment.pixiv.net Critical
- premium.pixiv.net Critical
- sensei.pixiv.net Critical
- sketch.pixiv.net Critical
- vroid.com Critical
- www.pixiv.net Critical
Wildcard domains 1
- *.fanbox.cc Critical
Out of scope (3)
- ads.pixiv.net
- factory.pixiv.net
- *.pixiv.co.jp
Rules
What the policy asks of you, and the bug types it won't reward, quoted from pixiv (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
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.
-
Denial of service
-
Social engineering (including phishing) of pixiv staff or contractors
-
Any physical attempts against pixiv property or data centers
-
Re-uploading other users' assets such as drawings and 3D models for testing of pixiv features
-
It is not permitted to publicly disclose reports without the express consent of pixiv's security team.
Not accepted
-
Hypothetical or theoretical vulnerabilities without actual verification code
-
Insecure coding or design patterns without actual vulnerabilities
-
Vulnerabilities with capability of brute force against password or tokens
-
Password, email and account policies, such as email id verification, reset link expiration, password complexity
-
Login/Logout CSRF
-
CSRF on forms that are available to anonymous users (e.g. contact form)
-
Vulnerabilities found in domains out-of-scope
-
Vulnerabilities affecting outdated browsers or platforms
-
Presence of autocomplete attribute on web forms
-
Missing secure flags on non-sensitive cookies
-
Reports of insecure SSL/TLS ciphers
-
Vulnerabilities with capability of username/email enumeration
-
Descriptive error messages (e.g. Stack traces, application or server errors)
-
Banner disclosure on servers
-
Misconfiguration of SPF record, DMARC and DKIM
-
Lack of security headers without an actual attack scenario
-
Phishing attack via registration email (e.g. making username a URL)
-
Tabnabbing
-
Disclosure of pixiv's numeric ID such as user ID and illustration ID (unless it compromises user privacy)
-
Lack of rate limit
-
Assets remaining visible on CDN after changing its visibility from public to private
-
Manipulating number of views
-
Insufficient session expiration
-
Backup of app data
-
Race conditions which do not involve privacy or monetary risk
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 43 minutes ago.
-
Cut
Top reward $7,500 to $5,000.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Reward cut
Maximum $7,500 → $5,000
-
Reward terms
The reward table or payout terms were edited
-
Reward terms
High $3,000 → $2,000, Medium $500 → $400
Public CVEs
Published vulnerabilities in this vendor's products, from the 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 hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
No technology is perfect, and pixiv believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. If you believe you've found a security issue in our product or service, we encourage you to notify us. We welcome working with you to resolve the issue promptly.
Disclosure Policy
- Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.
- It is not permitted to publicly disclose reports without the express consent of pixiv's security team.
- 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.
Program Rules
While researching, we'd like to ask you to refrain from:
-
Denial of service
-
Spamming (Examples include, but are not limited to, the following):
- Sending unintelligible messages or comments to general users. (If an investigation requires multiple actors, please prepare multiple accounts of your own to avoid involving general users.)
- Exposing your investigation to the public by modifying third-party or public resources. (While we understand this can be challenging due to the nature of social networking services, please ensure that your activities remain as discreet as possible.)
-
Social engineering (including phishing) of pixiv staff or contractors
-
Any physical attempts against pixiv property or data centers
-
Re-uploading other users' assets such as drawings and 3D models for testing of pixiv features
If spam or other disruptive behavior is detected, we may take the same actions as we do with regular spammers, such as account suspension. Furthermore, if such prohibited or disruptive acts are discovered during the reporting process, no bounty will be awarded.
Out of Scope / Known Issues
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
- Hypothetical or theoretical vulnerabilities without actual verification code
- Insecure coding or design patterns without actual vulnerabilities
- Vulnerabilities with capability of brute force against password or tokens
- Password, email and account policies, such as email id verification, reset link expiration, password complexity
- Login/Logout CSRF
- CSRF on forms that are available to anonymous users (e.g. contact form)
- Vulnerabilities found in domains out-of-scope
- Vulnerabilities affecting outdated browsers or platforms
- Presence of autocomplete attribute on web forms
- Missing secure flags on non-sensitive cookies
- Reports of insecure SSL/TLS ciphers
- Vulnerabilities with capability of username/email enumeration
- Descriptive error messages (e.g. Stack traces, application or server errors)
- Banner disclosure on servers
- Misconfiguration of SPF record, DMARC and DKIM
- Lack of security headers without an actual attack scenario
- Phishing attack via registration email (e.g. making username a URL)
- Tabnabbing
- Disclosure of pixiv's numeric ID such as user ID and illustration ID (unless it compromises user privacy)
- Lack of rate limit
- Assets remaining visible on CDN after changing its visibility from public to private
- Manipulating number of views
- Insufficient session expiration
- Backup of app data
- Race conditions which do not involve privacy or monetary risk
- IDOR which do not involve privacy or monetary risk (e.g. bookmarking private contents while gaining no information about it)
- Lack of URL confirmation on outgoing links
- Content subject to client-side filtering, such as age-restricted content, can be accessed by using the API directly. (Note: Age restrictions and client-side settings are fully adjustable and do not constitute restrictions requiring authentication or authorization.)
- Broken link hijacking (social media account etc): You may submit a report for this issue and it will be closed as informative, not eligible for bounty
- Misuse of the outgoing link URL confirmation page to generate links to arbitrary external websites.
- Credentials for PIXIV Accounts
- Investigation reports that are deemed to have used insider information, such as from employees, are not eligible for a reward.
Duplicate Reports
When we receive multiple reports concerning the same underlying cause, the eligibility for a bounty for later reports will be evaluated based on the value of new information provided to us. Any report that does not offer new value beyond what was included in an earlier report will be considered a duplicate and will be closed.
Safe Harbor
Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
Thank you for helping keep pixiv and our users safe!