msp / userlockout
msp/userlockout
Brute force prevention system for Magento2 - Member of MageSpecialist SecuritySuite
MSP UserLockout
Customer login brute force protection module.
This module can temporary lock a customer account when too many login password attempts fail are detected.
Member of MSP Security Suite
See: https://github.com/magespecialist/m2-MSP_Security_Suite
Installing on Magento2:
1. Install using composer
From command line:
composer require msp/userlockout
php bin/magento setup:upgrade
2. Enable and configure from your Magento backend config
Frontend screenshot
When the amount of failed attempts is reached, this module prevents further attemps for a defined amount of seconds.
This is one of the most effective countermeasures for brute force.
Backend manual unlock
You can monitor and manually unlock users from your Magento backend under Customers > Locked Users:
Command-line unlock
You can manually unlock one user from command-line if necessary:
php bin/magento msp:security:lockout:unlock <IP> <username>
Example:
php bin/magento msp:security:lockout:unlock 127.0.0.1 [email protected]
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.1.1 | stable | Fail | Not yet tested Details | 2017-09-07 16:10:27 |
| 1.1.0 | stable | Not tested | Not yet tested Details | 2017-07-31 16:07:31 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2017-05-31 16:13:31 |
| 0.1.2 | stable | Not tested | Not yet tested Details | 2017-05-07 16:09:27 |
| 0.1.1 | stable | Not tested | Not yet tested Details | 2016-07-15 13:45:17 |
| 0.1.0 | stable | Not tested | Not yet tested Details | 2016-07-15 13:19:47 |
Requires 3
| Package | Constraint |
|---|---|
| php | ^7.0|^7.1 |
| msp/security-suite-common | >=1.3 |
| magento/magento-composer-installer | * |
Suggests 1
| Package | Reason |
|---|---|
| msp/security-suite | Full MageSpecialist Security Suite |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | not tested | not tested | ||
| 2.4.8 | not tested | not tested | ||
| 2.4.9 | not tested | not tested |
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — a phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
More from msp
View vendorTurn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.