browsebit - 45% Detection Rate *

Did you just run into a download or a file on your computer that has a digital signature from browsebit? Some of the security products refers to the detected files as Adware.SwiftBrowse.CH and Adware.SwiftBrowse.CX. The detection rate for the browsebit files collected here is 45%. Please read on for more details.

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

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

You can view the additional details from the browsebit digital signature with the following steps:

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

Here is a screenshot of a file signed by browsebit:

Screenshot of the browsebit certificate

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

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

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

browsebit Files

These are the browsebit files I have gathered, thanks to the FreeFixer users.

Detection RatioFile Name
39/55{0fda9c93-3a61-4e7b-9de1-48ce3054563e}w64.sys
39/57maintainer.exe
17/56{26b8f333-820a-48b4-aa9a-a6a76289f88a}w64.sys
33/57{1e0c8639-131a-404e-bbfe-49359acd100b}w64.sys
27/55DealKeeper.BrowserAdapter.exe
32/57updatedealkeeper.exe
13/55{0fda9c93-3a61-4e7b-9de1-48ce3054563e}w64.sys

Scanner and Detection Names

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

ScannerDetection Names
ALYacAdware.SwiftBrowse.CH, Adware.SwiftBrowse.CX
AVGAdPlugin.DAI, AdPlugin.CWT, Browsebit.313
AVwareTrojan.Win32.Generic!BT, Yontoo (fs)
Ad-AwareAdware.SwiftBrowse.CH, Adware.SwiftBrowse.CX, Gen:Variant.Adware.Graftor.159320
AgnitumRiskware.Agent!
AhnLab-V3Win-PUP/BrowseFox.Gen, PUP/Win32.BrowseFox, Adware/Win32.SwiftBrowse
Antiy-AVLGrayWare[NetTool:not-a-virus]/Win64.NetFilter.a, GrayWare[AdWare]/Win32.DealKeeper.a, GrayWare[AdWare:not-a-virus,HEUR]/Win32.Kranet
ArcabitPUP.Adware.browsebit, Adware.SwiftBrowse.CX
AvastMSIL:BrowseFox-AE [PUP], Win32:BrowseFox-IT [PUP], Win32:BrowseFox-BM [PUP]
AviraADWARE/BrowseFox.Gen7, ADWARE/BrowseFox.Gen
Baidu-InternationalHacktool.Win64.NetFilter.A, Adware.Win32.BrowseFox.BD, Adware.Win32.BrowseFox.BSig, Adware.Win32.BrowseFox.BP, Adware.MSIL.BrowseFox.G
BitDefenderAdware.SwiftBrowse.CH, Adware.SwiftBrowse.CX, Gen:Variant.Adware.Graftor.159320
BkavW64.HfsAdware.BBEC, W32.HfsAdware.BBEC
ClamAVWin.Adware.Swiftbrowse-497, Win.Adware.Agent-41785, Win.Adware.Agent-23141
ComodoApplication.Win32.BrowseFox.AHJ
CyrenW64/A-59c9c70a!Eldorado, W32/S-11fc74d1!Eldorado, W32/S-bc825f4f!Eldorado
DrWebTrojan.Yontoo.1734, Tool.NetFilter.313, Trojan.BPlug.218
ESET-NOD32a variant of Win64/NetFilter.A potentially unsafe, Win32/BrowseFox.BD potentially unwanted, a variant of Win64/BrowseFox.CG, a variant of Win32/BrowseFox.P, a variant of MSIL/BrowseFox.G potentially unwanted
EmsisoftAdware.SwiftBrowse.CH (B), Adware.SwiftBrowse.CX (B), Gen:Variant.Adware.Graftor.159320 (B)
F-ProtW64/A-59c9c70a!Eldorado, W32/S-11fc74d1!Eldorado, W32/A-c74c8eb1!Eldorado, W32/S-bc825f4f!Eldorado
F-SecureAdware.SwiftBrowse.CH, Adware.SwiftBrowse.CX, Gen:Variant.Adware.Graftor.159320
FortinetAdware/BrowseFox
GDataAdware.SwiftBrowse.CH, Adware.SwiftBrowse.CX, Gen:Variant.Adware.Graftor.159320
IkarusPUA.MSIL.BrowseFox
JiangminAdWare/SwiftBrowse.ssl
K7AntiVirusAdware ( 0040f9f21 ), Adware ( 004b92811 ), Trojan ( 004a0a671 ), Adware ( 700000121 ), Trojan ( 004b03581 )
K7GWAdware ( 0040f9f21 ), Adware ( 004b92811 ), Trojan ( 004a0a671 ), Hacktool ( 655367771 ), Trojan ( 004b03581 )
Kasperskynot-a-virus:NetTool.Win64.NetFilter.k, not-a-virus:AdWare.Win32.DealKeeper.a, not-a-virus:HEUR:AdWare.Win32.Kranet.heur
MalwarebytesPUP.Optional.BrowseFox, PUP.Optional.BrowseBit.C
McAfeeArtemis!E9144F2C03DA, BrowseFox-FXS, Artemis!D2F25A295C4A, PUP-FNK, Artemis!99954386DE9B
McAfee-GW-EditionBehavesLike.Win64.PUPAmonetize.ph, BrowseFox-FXS, PUP-FNK
MicroWorld-eScanAdware.SwiftBrowse.CH, Adware.SwiftBrowse.CX, Gen:Variant.Adware.Graftor.159320
NANO-AntivirusRiskware.Win64.NetFilter.djojvo, Trojan.Win32.Yontoo.dpmcsm, Riskware.Win64.NetFilter.djngbx, Riskware.Win32.Kranet.dgvivv, Riskware.Win32.BPlug.djpkri
PandaTrj/Chgt.M, Trj/CI.A
Qihoo-360HEUR/QVM10.1.Malware.Gen, HEUR/QVM03.0.Malware.Gen
RisingPE:Adware.BrowserFox!1.A127 [F], PE:AdWare.Win32.BrowseFox.i!1075357760
SUPERAntiSpywareAdware.SwiftBrowse/Variant, Adware.BrowseFox/Variant
SophosBrowse Fox (PUA)
SymantecPUA.Yontoo.C, Trojan.Gen.2
TencentWin32.Trojan.Falsesign.Ajbg, Win32.Trojan.Falsesign.Wstm, Win32.Trojan.Falsesign.Hvtd, Win32.Trojan.Falsesign.Hviz
TrendMicroPUA_BROWSEFOX, TROJ_GEN.R0C1C0PHF15, TROJ_GEN.R0C1C0EA115
TrendMicro-HouseCallPUA_BROWSEFOX, TROJ_GEN.R0C1C0EA115, Suspicious_GEN.F47V1128
VBA32AdWare.DealKeeper, AdWare.Agent
VIPRETrojan.Win32.Generic!BT, Yontoo (fs)
ZillyaAdware.Yotoon.Win64.14, Adware.Agent.Win32.52012, Adware.Agent.Win32.14825
nProtectTrojan-Clicker/W32.Yotoon.48784, Trojan-Clicker/W32.Yotoon.128240.B, Adware.SwiftBrowse.CH, Trojan-Clicker/W32.Kranet.98544, Adware.SwiftBrowse.CX

* How the Detection Percentage is Calculated

The detection percentage is based on the fact that I have gathered 726 scan results for the browsebit files. 327 of these scan reports came up with some sort of detection. You can review the full details of the scan reports by examining the files listed above.

Analysis Details

The analysis has been done on certificates with the following serial numbers:

Comments

No comments posted yet.

Leave a reply