280. Hunting for Suspicious TLDs

Hello everyone!

We already looked how to use parts of URLs in our threat hunting missions, let's look at another similar artefact - TLDs.

In some cases adversaries use quite exotic TLDs for their infrastructure. Let's look at a recent example related to Rhadamanthys (yes, again). Most of the domains have quite suspicious TLDs, for example:

  • cloud341[.]autos
  • cloud341[.]baby
  • cloud341[.]icu
  • cloud341[.]lol
  • cloud341[.]monster
  • cloud34221[.]hair
  • cloud34221[.]homes
  • cloud34221[.]quest
  • cloud343[.]boats
  • cloud9342[.]beauty

Worth a hunting query, right?

event_type: "dnsreqwin"

AND

dns_rname: (*.autos OR *.baby OR *.icu OR *.lol OR *.monster OR *.hair OR *.homes OR *.quest OR *.boats OR *.beauty)

See you tomorrow!


Comments

Post a Comment

Popular posts from this blog

391. Hunting for TeamPCP's Stealer

Image
Hello everyone! What do I know about stealers? They seem to be very noisy! And today, we’ll once again see that in action using TeamPCP (Haze Wolf) as an example. This time , the stealer was implanted by attackers into three versions of the xinference package (2.6.0, 2.6.1, and 2.6.2). Essentially, it collects SSH keys, various credentials, environment variables, crypto wallets, and much more, then uses cURL for exfiltration. Let’s take a look at a couple of techniques the attackers used to obtain credentials. For example, they were interested in data stored in environment variables: env | grep AWS_ env | grep -i google env | grep -i gcloud env | grep -i azure This looks fairly suspicious from a detection perspective: event_type: processcreate* AND proc_file_path: "env" AND cmdline: ("grep" AND ("aws_" OR "google" OR "azure" OR "gcloud")) Another technique was abusing kubectl to obtain credentials: kubectl get secrets --all-n...
Read more

343. Ransomware Gangs Abuse SystemSettingsAdminFlows to Evade Defenses

Image
Hello everyone! Today we'll look at another example of how adversaries abuse legitimate Windows executables to evade defenses. This time it's  SystemSettingsAdminFlows.exe . According to this report , DeadLock leveraged this utility to disable various features of Windows Defender: SystemSettingsAdminFlows.exe Defender RTP 1  SystemSettingsAdminFlows.exe Defender SpynetReporting 0  SystemSettingsAdminFlows.exe Defender SubmitSamplesConsent 0  SystemSettingsAdminFlows.exe Defender DisableEnhancedNotifications 1 The commands disable Real-Time Protection (RTP) and cloud-based protections, stops the machine from sending threat reports to Microsoft, and prevent Windows Defender from automatically submitting suspicious files for analysis. Worth a query, isn't it? event_type: "processcreatewin" AND proc_file_path: "systemsettingsadminflows.exe" AND cmdline: "defender" See you tomorrow!
Read more

324. Adversaries Use HideMouse to Hide Evidence of Remote Access

Image
Hello everyone! We are often talking about how adversaries abuse RMMs, so let's talk a bit about a curious case of how they hide evidence of remote access. According to this report , the threat actors used HideMouse - an utility, which allows to hide mouse cursor movement, so the can use ScreenConnect they installed previously. Another hunting (or even detection!) opportunity, right? event_type: "processcreatewin" AND proc_file_productname: "HideMouse" See you tomorrow!
Read more