Current answer
Central 1 experienced a none incident: INC231919 -- MDSB delegates being locked out. The provider currently marks this incident Investigating.
Looking for an update now? Check the current status, or follow Central 1 for future changes.
Incident Lifecycle
Affected Components
Digital Banking Services
Incident Timeline
Investigating
Forge/MemberDirect has been experiencing a series of brute force attacks over the past several days. The attacks appear to be focused on gaining access to small business delegate accounts. This has resulted in hundreds of delegate accounts being locked by Forge. To restore access requires that the delegate contact the signer who has the authority to reinstate their login. There is no apparent correlation between these attacks and the customers impacted by the security incident last weekend.
For your reference, there are several safeguards against unauthorized access:
-- Forge/MD locks out a user after three unsuccessful login attempts (this is why so many organizations have had their delegate accounts locked).
-- Most of our customers have implemented strong password controls. If your organization has not implemented strong PAC, we would highly recommend that you do so.
-- If a threat actor is successful in logging in, we have put an additional control in place that requires that any device that has not been used to access the account previously will be forced through a two factor authentication.
There are also safeguards against unauthorized money movement:
-- Delegates only have authority to initiate transactions, not to approve them. So signers still need to approve new or changed payees.
-- eTransfers have built-in limits that restrict the amount of funds that can be transferred.
-- As an additional control, many organizations have also implemented 2SV on transactions. This will generally require a one time password if a user adds or changes a payee. If your organization has not implemented this control, we recommend that you do so.
Further questions can be directed to your relationship manager or contact info below. Thank you for your patience and understanding.
DigitalBanking_Support@Central1.com
1.888.889.7878 (option 2)
For your reference, there are several safeguards against unauthorized access:
-- Forge/MD locks out a user after three unsuccessful login attempts (this is why so many organizations have had their delegate accounts locked).
-- Most of our customers have implemented strong password controls. If your organization has not implemented strong PAC, we would highly recommend that you do so.
-- If a threat actor is successful in logging in, we have put an additional control in place that requires that any device that has not been used to access the account previously will be forced through a two factor authentication.
There are also safeguards against unauthorized money movement:
-- Delegates only have authority to initiate transactions, not to approve them. So signers still need to approve new or changed payees.
-- eTransfers have built-in limits that restrict the amount of funds that can be transferred.
-- As an additional control, many organizations have also implemented 2SV on transactions. This will generally require a one time password if a user adds or changes a payee. If your organization has not implemented this control, we recommend that you do so.
Further questions can be directed to your relationship manager or contact info below. Thank you for your patience and understanding.
DigitalBanking_Support@Central1.com
1.888.889.7878 (option 2)
Nov 13, 2026 at 10:21 PM UTC
Was your business affected by this Central 1 outage?
Follow Central 1 and route available status alerts to email or a team channel.