|
| 1 | +--- |
| 2 | +date: '2026-04-02T12:00:00.000Z' |
| 3 | +category: announcements |
| 4 | +title: Security Bug Bounty Program Paused Due to Loss of Funding |
| 5 | +layout: blog-post |
| 6 | +author: The Node.js Project |
| 7 | +--- |
| 8 | + |
| 9 | +The Node.js project's security bug bounty program is being paused due to the |
| 10 | +discontinuation of its external funding source. |
| 11 | + |
| 12 | +## Background |
| 13 | + |
| 14 | +Since 2016, the Node.js project has participated in the |
| 15 | +[Internet Bug Bounty (IBB)](https://www.hackerone.com/internet-bug-bounty) program |
| 16 | +through HackerOne, offering monetary rewards to security researchers who responsibly |
| 17 | +disclosed vulnerabilities in Node.js. The program was a meaningful part of our |
| 18 | +security ecosystem, and we're grateful to the researchers who participated. |
| 19 | + |
| 20 | +## Why |
| 21 | + |
| 22 | +The Internet Bug Bounty (IBB) program, which supported bounty rewards for Node.js |
| 23 | +through a pooled donation-funded initiative, has been paused. |
| 24 | +You can read more about the pause [here](https://hackerone.com/ibb?type=team). |
| 25 | +This decision was not made by the Node.js project. |
| 26 | + |
| 27 | +As a volunteer-driven open-source project, Node.js does not have an independent |
| 28 | +budget to sustain a bounty program on its own. Without external support, we are |
| 29 | +not able to offer monetary rewards for vulnerability reports at this time. |
| 30 | + |
| 31 | +## What This Means |
| 32 | + |
| 33 | +- **Security reporting remains unchanged.** We still accept and triage vulnerability |
| 34 | + reports through [HackerOne](https://hackerone.com/nodejs). If you discover a |
| 35 | + security issue, please continue to report it responsibly. |
| 36 | +- **No monetary rewards.** Reports will no longer be eligible for bounty payouts. |
| 37 | +- **Same commitment to security.** The Node.js Security Team continues to treat |
| 38 | + security with the highest priority. Our disclosure policy, response times, and |
| 39 | + release process remain the same. |
| 40 | + |
| 41 | +## A Thank You to Researchers |
| 42 | + |
| 43 | +We want to sincerely thank every researcher who has reported vulnerabilities through |
| 44 | +the bounty program over the years. Your contributions have made Node.js safer for |
| 45 | +millions of users. We hope you will continue to report security issues even without |
| 46 | +financial incentives — responsible disclosure is critical to the health of the |
| 47 | +open-source ecosystem. |
| 48 | + |
| 49 | +## Looking Ahead |
| 50 | + |
| 51 | +We will re-evaluate resuming the bounty program if dedicated funding becomes |
| 52 | +available again. If your organization depends on Node.js and is interested in |
| 53 | +sponsoring a bug bounty program, please reach out through the |
| 54 | +[OpenJS Foundation](https://openjsf.org/). |
| 55 | + |
| 56 | +For questions or to report a vulnerability, see our |
| 57 | +[security reporting page](/about/security-reporting). |
0 commit comments