Anybody else seeing Microsoft Azure Active Directory Connect account bruteforce?
AADSignInEventsBeta
| where Application == “Microsoft Azure Active Directory Connect”
In particular error code 50126 and 50053
Anybody else seeing Microsoft Azure Active Directory Connect account bruteforce?
AADSignInEventsBeta
| where Application == “Microsoft Azure Active Directory Connect”
In particular error code 50126 and 50053
@GossiTheDog Yes, started 23/10. All VN + RU addresses, but each IP is only seen once.
For clarity on this one, there’s no reason standard users or admins should be logging in with the Microsoft Azure Active Directory Connect app - it looks like low grade brute force to me.
I think Microsoft security peeps may want to go through their logs for Microsoft Azure Active Directory Connect app usage from 23rd October 2024 onwards - we’re all seeing the same thing, low and slow brute force, comes up as single factor auth (probably because Entra AD Connect is needed for directory sync for MFA to function).
@GossiTheDog Same. All hits are RU and VN using the browser "Rich Client 4.36.0.0".
@GossiTheDog Multiple hundred attempts in the last 30 days, 90% from RU, some from VN. All used accounts are known to having leaked credentials in the last few years. Is MFA forced for the AAD Connect app in the security defaults?
@GossiTheDog Yes can see events from 23/10 but not a large volume. All VN + RU IP addresses.
@GossiTheDog We started running these queries on the 14th after seeing this shared on H-ISAC, saw plenty of errors from RU, VN and then it just stopped - not sure if anyone else saw it stop on the 14th
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.