Home Cyber Security News FBI To Share Pwned Passwords With HIBP As It Goes Open Source

FBI To Share Pwned Passwords With HIBP As It Goes Open Source

by Abeerah Hashim

The popular resource helping people with managing breached passwords, Have I Been Pwned, brings some interesting updates. At first, Troy Hunt has announced making HIBP open source. Secondly, the FBI has pledged to officially share all pwned passwords with HIBP.

HIBP Goes Open Source

In a recent post, Troy Hunt, the founder of “Have I Been Pwned” has announced the changes in the service.

As revealed, HIBP will be available as open-source via the .NET Foundation. It’s an independent non-profit organization supporting the open-source ecosystem around the .NET framework.

Stating about the significance of this move, about Hunt already hinted months ago, the post reads,

It’s now an important part of many online services and this move ensures that anybody can run their own Pwned Passwords instance if they so choose.

FBI To Share Data With HIBP

Alongside making the HIBP code open-source, another major update to the service adding more credibility to it is its collaboration with the FBI.

Specifically, the FBI will be directly adding the pwned passwords they come across into the HIBP database. This will further broaden the scope of HIBP. Plus, it’ll also facilitate quickly updating the HIBP database with pwned passwords. In turn, it will help users stay informed about more breached passwords in a short time.

About this collaboration, Bryan A. Vorndran, Assistant Director, Cyber Division, FBI, provided the following statement to Troy Hunt.

We are excited to be partnering with HIBP on this important project to protect victims of online credential theft. It is another example of how important public/private partnerships are in the fight against cybercrime.

This collaboration that will give another entity the ability to update the database of pwned passwords, together with making the service open source, requires some code writing. Hunt has shared the details of the planned steps the code should power.

Together with all this, the .NET Foundation and Cloudflare will continue supporting the project as required.

You may also like

Latest Hacking News

Privacy Preference Center


The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis.

cookie_notice_accepted and gdpr[allowed_cookies] are used to identify the choices made from the user regarding cookie consent.

For example, if a visitor is in a coffee shop where there may be several infected machines, but the specific visitor's machine is trusted (for example, because they completed a challenge within your Challenge Passage period), the cookie allows Cloudflare to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does not store any personally identifiable information.

__cfduid, cookie_notice_accepted, gdpr[allowed_cookies]


DoubleClick by Google refers to the DoubleClick Digital Marketing platform which is a separate division within Google. This is Google’s most advanced advertising tools set, which includes five interconnected platform components.

DoubleClick Campaign Manager: the ad-serving platform, called an Ad Server, that delivers ads to your customers and measures all online advertising, even across screens and channels.

DoubleClick Bid Manager – the programmatic bidding platform for bidding on high-quality ad inventory from more than 47 ad marketplaces including Google Display Network.

DoubleClick Ad Exchange: the world’s largest ad marketplace for purchasing display, video, mobile, Search and even Facebook inventory.

DoubleClick Search: is more powerful than AdWords and used for purchasing search ads across Google, Yahoo, and Bing.

DoubleClick Creative Solutions: for designing, delivering and measuring rich media (video) ads, interactive and expandable ads.



The _ga is asssociated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners.

The _gat global object is used to create and retrieve tracker objects, from which all other methods are invoked. Therefore the methods in this list should be run only off a tracker object created using the _gat global variable. All other methods should be called using the _gaq global object for asynchronous tracking.

_gid works as a user navigates between web pages, they can use the gtag.js tagging library to record information about the page the user has seen (for example, the page's URL) in Google Analytics. The gtag.js tagging library uses HTTP Cookies to "remember" the user's previous interactions with the web pages.

_ga, _gat, _gid