Alias/esEmail-Worm.Win32.Bagle.cy [KAV], Troj/Bagle.CU [Antivir], Troj/BagleDL-U [Sophos], TROJ_BAGLE.DA [Trend], Trojan.Tooso.O [NAV], W32/Bagle.CJ-mm, W32/Bagle.CJ@mm [BitDefender], W32/Mitglieder.FE [F-Prot], Worm.Bagle.BS [ClamAV] |
Visible Symptoms
|
Detailed AnalysisThis variant of Bagle was spammed to numerous email recipients on September 19, 2005. It may have arrived as an attachment to an email message either as an .EXE file or .ZIP file. The Trojan (if run) will write a copy of itself to the system and also extract a .DLL component. The .DLL component code is injected into the Windows shell (EXPLORER.EXE) in order to make its code stealthy. This threat is coded to attempt to retrieve a binary file from one of a number of hard-coded web sites. At the time of this writing, the file retrieve process failed due to the file not being present on the servers, or the servers were unreachable. Load at Windows Startup
This Trojan modifies the registry to auto load the Trojan at each Windows logon or startup -
This Trojan creates an additional registry key data entry -
This could be an internal counter for use by the Trojan to know if it has run once only or has executed more than once. Security application termination
File modifications
File download routine Process injection |
Recommended Action
FortiGate systems: |