Quicknode believes the future of
the Internet is private, trustless, and
censorship-resistant.
Our mission is to help blockchain ecosystems scale, by
providing accessible core infrastructure.
We make it simple to power your blockchain applications
and scale up as you grow. From elastic APIs, to powerful
tools & analytics, all at your command through a simple
control panel.
Responsible Disclosure
Quicknode considers trust and the protection of our customers' data as a highest priority. Therefore, Quicknode takes the security of our systems extremely seriously.
Quicknode's Responsible Disclosure Policy
Quicknode looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.
Response Targets
Quicknode will make a best effort to meet the following SLAs for hackers participating in our program:
Type of Response SLA in business days
First Response: 5 days
Time to Triage: 10 days
Time to Resolution: depends on severity and complexity
We'll try to keep you informed about our progress throughout the process.
Disclosure Policy
As this is a private program, please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
Follow HackerOne's disclosure guidelines.
Program Rules
Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced).
Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
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.
Out of Scope Vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
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.