Skip to main content

WPBiff

Wordpress Two-Factor Authentication Brute-forcer

Travis CI Requirements Status Python Versions

Features

This utility brute-forces two-factor protected Wordpress dashboards by iterating through every possible 6-digit Google Authenticator TOTP token.

WPBiff is meant to be used together with Main-in-the-Middle based attacks against NTP.

Supported Plugins

WPBiff is able to brute-force Wordpress login pages protected by the following two-factor authentication plugins:

Installing WPBiff

The latest package is available on PyPI

$ pip install wpbiff

Requirements

This utility runs on Python 2.6 and 2.7

Usage Instructions

In order to carry out successful attack against a two-factor protected Wordpress blog, you must satisfy the following two pre-requisites.

Pre-requisites

The first requirement is that you must have the login username and password to the Wordpress dashboard on /wp-admin. The credentials can be acquired by phishing, key logging or password reuse.

Secondly, you must be able to control the internal clock of the target server. I recommend Delorean to fixate the server time to a certain point. You must fixate an arbitrary date with the -d flag with Delorean and use the very same time stamp with WPBiff in parallel.

For more information on remote clock tampering, please refer to this blog entry (coming soon).

Options

The following section explains the basic usage of WPBiff. You can also use the -h switch any time to get help.

-d, --date DATE

Pinned date (Format: “YYYY-MM-DD hh:mm”) [required]

-u, --username USER

Wordpress username [required]

-p, --password PASS

Wordpress password [required]

-a, --user-agent

HTTP User-Agent header (default: Firefox)

-t, --token TOKEN

Initial value of token (default: 000000)

-m, --max-token TOKEN

Maximum token value (default: 999999)

Use the --plugin switch to choose between the Wordpress plugin type providing two-factor authentication for the target. Choose ga for Google Authenticator and wpga for WP Google Authenticator.

Examples

Assume NTP traffic can be intercepted between your target and the upstream NTP server. By tampering with this traffic, you can “pin” the target’s clock to a certain time and date.

Launch Delorean NTP server to serve a fixed time and date

$ ./delorean.py -d "2015-10-30 11:22"

Redirect NTP traffic from your target to the fake NTP server.

Finally launch WPBiff as the following

$ wpbiff -u admin -p admin -d "2015-10-30 11:22" --plugin ga "http://www.example.com"

This session will brute force Wordpress on www.example.com with the login username admin and password admin.

Once the process finishes, WPBiff dumps the valid token and the session cookies for accessing the Wordpress dashboard.

Contributors

Credits

Metadata

Release files for wpbiff 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for wpbiff 0.1.0
File Size Uploaded Provenance Actions
wpbiff-0.1.0.tar.gz 8.1 kB Without provenance Details for wpbiff-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for wpbiff 0.1.0
File Interpreter ABI Platform Actions
wpbiff-0.1.0-py2-none-any.whl Python 2 none any Details for wpbiff-0.1.0-py2-none-any.whl

Total release size: 20.8 kB

Release files / wpbiff-0.1.0.tar.gz

Download URL wpbiff-0.1.0.tar.gz
Size 8.1 kB
Tags Source
SHA-256 checksum
How to use checksums
5cd4b481401ce3d04fda9e79302c5f21be77efd42da809aa8b36709d45fcf838
BLAKE2b-256 checksum
How to use checksums
e4fc4867c5b0594dfa30960f8712b7015c22bba735b4e58adcda90bb05f6f995
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release files / wpbiff-0.1.0-py2-none-any.whl

Download URL wpbiff-0.1.0-py2-none-any.whl
Size 12.7 kB
Tags Python 2
SHA-256 checksum
How to use checksums
cad9c8e6baa2bdc85b0e164a39b3eb9a23c39bc35e733c12a68ac146c4cc02ac
BLAKE2b-256 checksum
How to use checksums
54002b63fe56f496b662dc6a3aa057b3e011c580dbe3c282b8341c8e16cdaa8c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for wpbiff 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page