ILS_ANONYMOUS_USER invited account used in CryptoVirus Attack

Hello,

We were just hit by an ncov cryptovirus (luckaly all our backups were fine). but the attack vector apears to be a login on an RDP server accessible via the web using an ILS_ANONYMOUS_USER account. Luckaly this account could only access shared files open to "everybody" and "authenticated users" (yes we have some bad NTFS security still hanging arround !)

I have no idea what this account is for, the only thing I know is that is was created on our AD on october 2003. I have deactivated it so avoid futur attacks.

My googling didn't result in much success on the account and i couldn't find any recent security alerts that could explain the intrusion (all our systems are up to date)

​

Could anybody give me some info on this account ? And an idea how a hacker could crack the password (the account was probably never touched since creation) ?

​

Ok, back to restoring files :-s

thanks for any help people can give me.

Posted May 10, 2020, 6:57 AM UTC

06
UBX_Cloud_Steve•

If your RDP server is exposed to your network edge without any type of proxy in front of it your going to get hacked again.

It’s less to do with the actual domain account then the security posture and exposure of that server.

Patch the server Block external access to TCP & UDP 3389 Don’t rely on security by obscurity Disable login rights to service accounts

Use a SSL or Client based VPN if people need access from the outside.

Place web facing things in the DMZ and only accessible by 443.

Place production back end systems in a different subnet and only open the traffic you need between the 2 zones.

Steve

12
Bad_Mechanic•

RDP should never be exposed directly to the internet. Unless you fix that, you're going to be successfully attacked again.

8
mwagner_00•

Sounds like it’s the IIS_Anonymous_User account. Probably given too many permissions. Kill IIS if you don’t need it. Close RDP.

2
disclosure5•

Can you check the date on this user's creation?

Googling this account, the second hit is this very page and the first doesn't seem to actually name it. I'm getting the view it was originally created by the attacker.

Regardless, if your domain has that much legacy lying around this will never cease being a problem. I'd highly recommend getting that RDP server set to allow only accounts with MFA setup.

1
starbugstoneOP•

thanks for the feedback, yeah we have a load of old stuff hanging around. time to do a spring clean.

The account was created the 01/10/2003.

1
schismsaints•

If you have a Microsoft account team, try to get an AD security audit. There are lots of legacy things like this in old domains that need to be cleaned up.

3