Check if a user password is found in the Have I Been Pwned database.

Installs: 119

Dependents: 1

Suggesters: 0

Security: 0


2.1.0 2023-11-14 01:49 UTC

This package is auto-updated.

Last update: 2024-06-07 10:56:19 UTC


This module is not a replacement for two factor authentication.

Users are actively locked out if their password is found to be pwnd and forced to reset their password.

Although it adds to the user security te enforce unique passwords, this module will not prevent any password leaks like the ones used by HaveIBeenPwned.


If this module breaks your website, you get to keep all the pieces.

Have I Been Pwned for SilverStripe

This module checks on password change and login, if the SHA1 of the password appears in the Have I Been Pwnd database.

There is never a full password transmitted to HaveIBeenPwned, only the first 5 characters of a SHA1 of the password, the response from HaveIBeenPwned is then compared locally.

Given the nature of HaveIBeenPwned, even if a password is intercepted (the connection is HTTPS and Troy Hunt is not the easiest when it comes to security), the password has already been out in the wild, so this scenario is a very unlikely one to cause more breaches.

Only a count of the amount of times the password shows in the database is collected, next to which known breaches contain the users Email or Username. This information about the password and the email are unrelated. HaveIBeenPwned does not provide a relation between the two. On purpose.


SilverStripe Framework 4.x+ GuzzleHttp 6.x+ PHP 8.0+


composer require firesphere/haveibeenpwnd


Making calls to the Have I Been Pwned API requires a key. There's a full blog post on why here.

To configure this module to use the key, define an environment variable on your server or your .env:


Other configurations can be done in YML:

Name: MyPwnConfig
    after: HaveIBeenPwnedConfig
  allow_pwnd: false
  save_pwnd: true
  environment: dev
  allow_pwnd: true


allow_pwnd If set to true, passwords that appear in the Have I been Pwnd database will be allowed

save_pwnd If set to true, all the breaches in which the user's username or email address appears

Applying the validator extension to other PasswordValidators

Add the following to either of your config yml files. (Suggested is using an extensions.yml file)

    - Firesphere\HaveIBeenPwned\Extensions\PasswordValidatorExtension

Replacing the vendor\namespace\validator with your own Validator namespace and classname

By default, if the default PasswordValidator isn't registered, this module will register it to make sure the changes are applied. You can override this in your own _config.php file.

Only environment

To not make engineers life impossible and allow for using pwnd passwords on local environments in dev mode, by default, the Pwnd service is turned off in dev mode

Can I USe

Simply put? Sure. Admitted, this is Open Source software, and in theory, you can use it any way you want.

You can license this work, by buying a usage subscription. It will allow you to request support, or just supporting the developer.

Did you read this entire readme? You rock!

Pictured below is a cow, just for you.

               /( ,,,,, )\
           .-"; ;;;;;;;;; ;"-.
           '.__/`_ / \ _`\__.'
              | (')| |(') |
              | .--' '--. |
              |/ o     o \|
              |           |
             / \ _..=.._ / \
            /:. '._____.'   \
           ;::'    / \      .;
           |     _|_ _|_   ::|
         .-|     '==o=='    '|-.
        /  |  . /       \    |  \
        |  | ::|         |   | .|
        |  (  ')         (.  )::|
        |: |   |;  U U  ;|:: | `|
        |' |   | \ U U / |'  |  |
        ##V|   |_/`"""`\_|   |V##
           ##V##         ##V##