Thursday, February 27, 2025
Homecyber securityHackerOne Apologized to Ukrainian Hackers After Blocking their Bounty Payouts

HackerOne Apologized to Ukrainian Hackers After Blocking their Bounty Payouts

Published on

SIEM as a Service

Follow Us on Google News

After sanctions were imposed on Russia and Belarus after Ukraine’s invasion, the CISO of HackerOne, Chris Evans, apologized to Ukrainian hackers for blocking their bug bounty payouts.

Bug bounty platform, HackerOne is blocking the bug bounty rewards, in some cases thousands of dollars, and rejecting the Ukrainian hackers to withdraw their earnings.

Following the Russian invasion of Ukraine in late February, HackerOne has blocked payouts to several hackers and researchers with affected HackerOne accounts due to all the economic sanctions and export controls that are imposed; however, all these imposed sanctions are not applicable to them.

In this event, HackerOne notified all the bounty hunters from Ukraine, Russia, and Belarus that all their transactions had been paused.

Apart from this, one of the Belarusian hackers claimed from its Twitter handle “xnwup” that “HackerOne took $25k from me because I am a Belarusian citizen.”

Here’s what HackerOne stated:-

“Due to current economic sanctions and export controls, if you are based in Ukraine, Russia, or Belarus, all communications and transactions (including swag shipping) have been paused for the time being.”

The HackerOne bug bounty program paid out more than $107 million in 2020 alone to all eligible bounty hunters. However, here the most vital point, in this case, is the dependency of several security researchers on their earnings to support their families.

Roleplay of HackerOne CEO

Earlier this week, HackerOne CEO MÃ¥rten Mickos brought up the freeze of Ukrainian accounts on the bug bounty platforms, saying that all rewards for hackers from sanctioned areas would go to UNICEF.

However, later, he deleted his tweet and published a new tweet in which he claimed that he misspoke the above statement, as he intended to say:-

“We re-route hacker rewards to donations only on specific instruction by the hacker.”

But, the CISO of HackerOne, Chris Evans, has published an official apology statement:-

“On behalf of the HackerOne team, I’d like to apologize to the Ukrainian hacker community for the frustration and confusion that our poor communication has caused. We have not (and will not) block lawful payments to Ukraine.”

Moreover, after this incident, HackerOne’s CISO, Chris Evans, also asserted that they would publish a FAQ page within 24 hours to brief this incident in detail.

You can follow us on Linkedin, Twitter, Facebook for daily Cybersecurity and hacking news updates.

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Lotus Blossom Hacker Group Uses Dropbox, Twitter, and Zimbra for C2 Communications

The Lotus Blossom hacker group, also known as Spring Dragon, Billbug, or Thrip, has...

Squidoor: Multi-Vector Malware Exploiting Outlook API, DNS & ICMP Tunneling for C2

A newly identified malware, dubbed "Squidoor," has emerged as a sophisticated threat targeting government,...

Unpatched Vulnerabilities Attract Cybercriminals as EDR Visibility Remains Limited

Cyber adversaries have evolved into highly organized and professional entities, mirroring the operational efficiency...

Threat Actors Attack Job Seekers of Fortune 500 Companies to Steal Personal Details

In Q3 2024, Cofense Intelligence uncovered a targeted spear-phishing campaign aimed at employees working...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Lotus Blossom Hacker Group Uses Dropbox, Twitter, and Zimbra for C2 Communications

The Lotus Blossom hacker group, also known as Spring Dragon, Billbug, or Thrip, has...

Squidoor: Multi-Vector Malware Exploiting Outlook API, DNS & ICMP Tunneling for C2

A newly identified malware, dubbed "Squidoor," has emerged as a sophisticated threat targeting government,...

Unpatched Vulnerabilities Attract Cybercriminals as EDR Visibility Remains Limited

Cyber adversaries have evolved into highly organized and professional entities, mirroring the operational efficiency...