Thursday, December 19, 2024
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

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.

- Advertisement - SIEM as a Service

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

Beware Of Malicious SharePoint Notifications That Delivers Xloader Malware

Through the use of XLoader and impersonating SharePoint notifications, researchers were able to identify...

Malicious Supply Chain Attacking Moving From npm Community To VSCode Marketplace

Researchers have identified a rise in malicious activity on the VSCode Marketplace, highlighting the...

Hackers Weaponizing LNK Files To Create Scheduled Task And Deliver Malware Payload

TA397, also known as Bitter, targeted a Turkish defense organization with a spearphishing email...

BADBOX Botnet Hacked 74,000 Android Devices With Customizable Remote Codes

BADBOX is a cybercriminal operation infecting Android devices like TV boxes and smartphones with...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

Beware Of Malicious SharePoint Notifications That Delivers Xloader Malware

Through the use of XLoader and impersonating SharePoint notifications, researchers were able to identify...

Malicious Supply Chain Attacking Moving From npm Community To VSCode Marketplace

Researchers have identified a rise in malicious activity on the VSCode Marketplace, highlighting the...

Hackers Weaponizing LNK Files To Create Scheduled Task And Deliver Malware Payload

TA397, also known as Bitter, targeted a Turkish defense organization with a spearphishing email...