IVPN preparing for 6th annual security audit

IVPN News By Nick Pestell | Posted on February 15, 2024

Consistent with our pledge to conduct a yearly review of our systems, we have commissioned the independent security auditing organisation Cure53 to perform a security audit in March 2024.

As we remarked last year, audits we arrange focus on parts of our systems that received significant updates. Accordingly, the scope of the sixth annual security audit will include:

The audit will be undertaken by 3 security auditors. We expect a conclusion for the audit and publication of results to happen within the next two months.

Nick Pestell CEO IVPN

Audit Apps Transparency
We invite you to discuss this post in our Reddit community or on Twitter. You can also send your feedback to blog@ivpn.net.
IVPN News

A security incident on our Bitcoin payment server

By IVPN Staff

IVPN News

Annual security audit scheduled for 2026

By Nick Pestell

Under the Hood

Unlinked Access: reducing cross-service account linkage with HSM-backed token derivation

By Juraj Hilje

IVPN News

A security incident on our Bitcoin payment server

Posted on August 11, 2026 by IVPN Staff

Summary: on 7 August a critical vulnerability was disclosed in BTCPay Server, the open-source software we self-host to accept Bitcoin payments. It was being exploited before disclosure, and we were among the merchants hit: an attacker extracted our Lightning node credentials and transferred out our operating funds.
Annual security audit scheduled for 2026
IVPN News

Annual security audit scheduled for 2026

Posted on June 19, 2026 by Nick Pestell

Consistent with our commitment to regular independent security audits, we have scheduled our eighth annual security audit with Cure53, to be conducted over the course of two weeks in July. As in previous years, audits target systems and services that have undergone significant updates and where review provides the most value to customers in terms of security and auditability.
Spotted a mistake or have an idea on how to improve this page?
Suggest an edit on GitHub.