sizlsearch - 21% Detection Rate *

Did you just run into a download or a file on your computer that is digitally signed by sizlsearch? Some of the security products refers to the detected files as Slizearch.436 and Adware.Win32.BrowseFox.D. The detection rate for the sizlsearch files collected here is 21%. Please read on for more details.

You will typically notice sizlsearch when clicking to run the file. The publisher name is then displayed as the "Verified publisher" in the UAC dialog as the screencap shows:

Screenshot where sizlsearch appears as the verified publisher in the UAC dialog

You can also view the sizlsearch certificate with the following steps:

  1. Open up Windows Explorer and locate the sizlsearch file
  2. Right-click the file and select Properties
  3. Click on the Digital Signatures tab
  4. Click the View Certificate button

Here is a screencap of a file digitally signed by sizlsearch:

Screenshot of the sizlsearch certificate

As you can see in the screenshot above, Windows reports that "This digital signature is OK". This means that the file has been published by sizlsearch and that no one has tampered with the file.

If you click the View Certificate button shown in the screengrab above, you can view all the details of the certificate, such as when it was issued, who issued the certificate, how long it is valid, etc. You can also examine the address for sizlsearch, such as the street name, city and country.

VeriSign Class 3 Code Signing 2010 CA has issued the sizlsearch certificates. You can also view the details of the issuer by clicking the View Certificate button shown in the screenshot above.

sizlsearch Files

The following are the sizlsearch files I have collected, thanks to the FreeFixer users.

Detection RatioFile Name
12/55sizlsearch.BRT.Helper.exe
8/55{9d5747ee-0448-4681-8337-1555de75a3b6}t.sys
3/54{9d5747ee-0448-4681-8337-1555de75a3b6}gw.sys
9/53{9d5747ee-0448-4681-8337-1555de75a3b6}gw64.sys
5/54{9d5747ee-0448-4681-8337-1555de75a3b6}gt64.sys
5/52{9d5747ee-0448-4681-8337-1555de75a3b6}gt.sys
30/53sizlsearchbho.dll
8/54{9d5747ee-0448-4681-8337-1555de75a3b6}gw64.sys
8/54utilsizlsearch.exe
5/53{9d5747ee-0448-4681-8337-1555de75a3b6}gw.sys
7/55sizlsearchUninstall.exe
13/54{9d5747ee-0448-4681-8337-1555de75a3b6}t.sys
20/55sizlsearch.PurBrowse.exe
7/55updatesizlsearch.exe
29/55sizlsearch.BrowserAdapter.exe
6/55updatesizlsearch.exe
10/54{9d5747ee-0448-4681-8337-1555de75a3b6}t.sys
4/52{9d5747ee-0448-4681-8337-1555de75a3b6}gw64.sys
4/52{9d5747ee-0448-4681-8337-1555de75a3b6}gw64.sys
7/54updatesizlsearch.exe

Scanner and Detection Names

Here's the detection names for the sizlsearch files. I've grouped the detection names by each scanner engine. Thanks to VirusTotal for the scan results.

ScannerDetection Names
AVGSlizearch.436, BrowseFox.F
AVwareYontoo (fs), Trojan.Win32.Generic!BT, Adware.BrowseFox
Ad-AwareGen:Variant.Adware.BHO.Agent.4, Adware.Mplug.AF
AgnitumPUA.Yotoon!, PUA.Agent!, Riskware.Agent!
AhnLab-V3PUP/Win32.SwiftBrowse, PUP/Win32.BrowseFox, PUP/Win32.DealKeeper, Adware/Win32.SwiftBrowse
AntiVirAPPL/BrowseFox.Gen2
Antiy-AVLGrayWare[AdWare:not-a-virus]/Win32.Agent, GrayWare[AdWare:not-a-virus,HEUR]/Win32.Kranet, Trojan/Win32.TSGeneric
AvastWin32:BrowseFox-BV [PUP], Win32:BrowseFox-BM [PUP]
AviraSPR/NetFilter.F, ADWARE/BrowseFox.Gen
Baidu-InternationalAdware.Win32.BrowseFox.D, Adware.Win32.Agent.ai, Adware.Win32.BrowseFox.BH, Adware.Win32.BrowseFox.BC
BitDefenderGen:Variant.Adware.BHO.Agent.4, Adware.Mplug.AF
ClamAVWin.Adware.Swiftbrowse-8, Win.Adware.Swiftbrowse-269, Win.Adware.Mplug-45, Win.Adware.Netfilter-130
ComodoApplication.Win32.Altbrowse.AK, Application.Win32.BrowseFox.JK
DrWebTrojan.BPlug.199, Trojan.BPlug.123, Trojan.BPlug.17, Trojan.BPlug.93, Trojan.BPlug.117, Trojan.BPlug.218
ESET-NOD32a variant of MSIL/BrowseFox.G, a variant of Win32/BrowseFox.F, a variant of Win32/BrowseFox.H, Win32/BrowseFox.C, a variant of Win32/BrowseFox.J, a variant of MSIL/BrowseFox.H, a variant of Win32/BrowseFox.P, a variant of Win64/BrowseFox.AZ
EmsisoftGen:Variant.Adware.BHO.Agent.4 (B), Adware.Mplug.AF (B)
F-ProtW32/A-dd00b781!Eldorado, W32/A-c74c8eb1!Eldorado
F-SecureGen:Variant.Adware.BHO.Agent.4, Adware.Mplug.AF
FortinetAdware/Agent
GDataGen:Variant.Adware.BHO.Agent.4, Adware.Mplug.AF
IkarusPUA.RiskWare.NetFilter, PUA.Elex, AdWare.SwiftBrowse, not-a-virus:AdWare.Win32.Agent, AdWare.SpadeCast
JiangminAdWare/Yotoon.m, AdWare/Yotoon.k
K7AntiVirusUnwanted-Program ( 00454f261 )
K7GWUnwanted-Program ( 00454f261 ), Trojan ( 020000001 )
Kasperskynot-a-virus:HEUR:AdWare.MSIL.Kranet.heur, not-a-virus:AdWare.Win32.Agent.ahbx, not-a-virus:HEUR:AdWare.Win32.Kranet.heur
KingsoftWin32.Troj.Generic.a.(kcloud), Win32.Troj.Agent.ah.(kcloud)
MalwarebytesPUP.Optional.Sizlsearch.A
McAfeeBrowseFox.b, Artemis!AA8161FB658B, Artemis!5A7BC20833C6, Artemis!B1C3AAA9E432, Artemis!46D64CF7B46C, Artemis!F93711E72896, BrowseFox, PUP-FNK, Artemis!CA2E4DF0058F
McAfee-GW-EditionBehavesLike.Win32.Backdoor.ch, Artemis!5A7BC20833C6, Artemis!B1C3AAA9E432, Artemis!46D64CF7B46C, BehavesLike.Win32.AdwareBrowseFox.dc, Artemis!F93711E72896, BehavesLike.Win32.Downloader.dh, BehavesLike.Win32.Adware.nh, Artemis!CA2E4DF0058F
MicroWorld-eScanGen:Variant.Adware.BHO.Agent.4, Adware.Mplug.AF
NANO-AntivirusRiskware.Win32.Agent.cqycvd, Trojan.Win32.BPlug.dcxxfx, Riskware.Win32.Kranet.dfqewc, Riskware.Win32.Kranet.denqfa
PandaTrj/CI.A
Qihoo-360Win32/Virus.Adware.e4c, Win32/Virus.Adware.639
RisingPE:Trojan.Win32.Generic.17102BDB!386935771
SUPERAntiSpywareAdware.BrowseFox/Variant, PUP.BrowseFox/Variant
SophosGeneric PUA HG, BrowseSmart, Browse Fox
TrendMicro-HouseCallSuspicious_GEN.F47V0819, Suspicious_GEN.F47V0702, TROJ_GEN.F47V0513, Suspicious_GEN.F47V0618, Suspicious_GEN.F47V0701, Suspicious_GEN.F47V0706, Suspicious_GEN.F47V0710, TROJ_GEN.F47V0508, Suspicious_GEN.F47V0626
VBA32AdWare.Win64.Yotoon, AdWare.Kranet, AdWare.Agent
VIPREYontoo (fs), Trojan.Win32.Generic!BT, Adware.Agent, Adware.BrowseFox
ZillyaAdware.Yotoon.Win64.10, Adware.Agent.Win32.9011, Adware.Agent.Win32.12828, Adware.Kranet.Win32.247
nProtectTrojan-Clicker/W32.LinkSwift.294176, Trojan-Clicker/W32.LinkSwift.98592

* How the Detection Percentage is Calculated

The detection percentage is based on that I've gathered 1673 scan reports for the sizlsearch files. 355 of these scan results came up with some sort of detection. If you like, you can review the full details of the scan results by examining the files listed above.

Analysis Details

The analysis is done on certificates with the following serial numbers:

Comments

No comments posted yet.

Leave a reply