Monitoring HTTP User-Agent fields
For a long time I've been recommending companies to use Intrusion Detection Systems to detect infected/malicious machines on their own networks – instead of detecting inbound attacks (which will definitely happen, and the number of alerts will be in hundreds, if not thousands) they should detect outbound attacks. This way they can early detect potentially compromised internal machines when they phone home or download second stage binaries.
Matt Jonkman from Emerging Threats (http://www.emergingthreats.net) has been publishing Snort rules that detect non-standard User-Agent headers for a long time (if you're not using the ET rules set you're missing a lot!).
While this still catches a lot of malware, recently I saw more samples pretending to be Microsoft's BITS (Background Intelligent Transfer Service) – the service that's downloading all those updates Microsoft publishes every month.
As Microsoft made the BITS API available to anyone, malware authors can use that easily to download their own binaries, instead of Windows patches. Here's an example of a malware using BITS to download second stage binary – notice the target Host: header.
So, while monitoring User-Agent fields is still helpful in catching infected machines, we can expect that malware authors will use legitimate services such as BITS even more in the future. One thing we can possibly do is monitor such requests and when they contain the BITS User-Agent field check the Host: header; it should be easy to build a white list of allowed hosts.
If you have other ideas about how to improve User-Agent monitoring let us know.
--
Bojan
Comments
Anonymous
Dec 3rd 2022
9 months ago
Anonymous
Dec 3rd 2022
9 months ago
<a hreaf="https://technolytical.com/">the social network</a> is described as follows because they respect your privacy and keep your data secure. The social networks are not interested in collecting data about you. They don't care about what you're doing, or what you like. They don't want to know who you talk to, or where you go.
<a hreaf="https://technolytical.com/">the social network</a> is not interested in collecting data about you. They don't care about what you're doing, or what you like. They don't want to know who you talk to, or where you go. The social networks only collect the minimum amount of information required for the service that they provide. Your personal information is kept private, and is never shared with other companies without your permission
Anonymous
Dec 26th 2022
9 months ago
Anonymous
Dec 26th 2022
9 months ago
<a hreaf="https://defineprogramming.com/the-public-bathroom-near-me-find-nearest-public-toilet/"> nearest public toilet to me</a>
<a hreaf="https://defineprogramming.com/the-public-bathroom-near-me-find-nearest-public-toilet/"> public bathroom near me</a>
Anonymous
Dec 26th 2022
9 months ago
<a hreaf="https://defineprogramming.com/the-public-bathroom-near-me-find-nearest-public-toilet/"> nearest public toilet to me</a>
<a hreaf="https://defineprogramming.com/the-public-bathroom-near-me-find-nearest-public-toilet/"> public bathroom near me</a>
Anonymous
Dec 26th 2022
9 months ago
Anonymous
Dec 26th 2022
9 months ago
https://defineprogramming.com/
Dec 26th 2022
9 months ago
distribute malware. Even if the URL listed on the ad shows a legitimate website, subsequent ad traffic can easily lead to a fake page. Different types of malware are distributed in this manner. I've seen IcedID (Bokbot), Gozi/ISFB, and various information stealers distributed through fake software websites that were provided through Google ad traffic. I submitted malicious files from this example to VirusTotal and found a low rate of detection, with some files not showing as malware at all. Additionally, domains associated with this infection frequently change. That might make it hard to detect.
https://clickercounter.org/
https://defineprogramming.com/
Dec 26th 2022
9 months ago
rthrth
Jan 2nd 2023
8 months ago