Whilokii - 24% Detection Rate *

Did you just run into a download or a file on your computer that has a digital signature from Whilokii? Some of the security products refers to the detected files as Adware.NetFilter.J and Browse Fox. The detection rate for the Whilokii files collected here is 24%. Please read on for more details.

You will probably see Whilokii when running the file. The publisher name is displayed as the "Verified publisher" in the UAC dialog as the screenshot shows:

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

You can view additional details from the Whilokii certificate with the following steps:

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

Here's a screenshot of a file digitally signed by Whilokii:

Screenshot of the Whilokii 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 Whilokii and that no one has tampered with the file.

If you click the View Certificate button shown in the screenshot above, you can examine 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 see the address for Whilokii, such as the street name, city and country.

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

Whilokii Files

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

Detection RatioFile Name
1/47Whilokiibho.dll
1/47updateWhilokii.exe
7/48updatewhilokii.exe
1/48Whilokiibho.dll
28/55maintainer.exe
5/48Whilokii.Common.dll
6/50updatewhilokii.exe
5/51updatewhilokii.exe
6/54updateWhilokii.exe
18/54{fed5e6b2-4fc4-43ba-8e95-001d959d8008}w64.sys
21/55{6cb9884f-9bf7-4457-8c28-23c7ccc9fa12}t.sys
8/54{fed5e6b2-4fc4-43ba-8e95-001d959d8008}t.sys
34/56maintainer.exe
26/56{6cb9884f-9bf7-4457-8c28-23c7ccc9fa12}w64.sys
25/55{6cb9884f-9bf7-4457-8c28-23c7ccc9fa12}t.sys
8/56updateWhilokii.exe
0/48Whilokiibho.dll

Scanner and Detection Names

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

ScannerDetection Names
ALYacAdware.NetFilter.J, Adware.BrowseFox.AT, Adware.SwiftBrowse.CH
AVGGeneric.7A9, Generic6.DAP, AdPlugin.DAI
AVwareYontoo (fs), Trojan.Win32.Generic!BT
Ad-AwareGen:Variant.Adware.SwiftBrowse.1, Adware.NetFilter.E, Adware.NetFilter.J, Adware.BrowseFox.AT, Adware.SwiftBrowse.CH
AgnitumTrojan.BPlug!, Riskware.Agent!, PUA.Yotoon!
AhnLab-V3Adware/Win32.Downloader, Adware/Win32.SwiftBrowse, Trojan/Win64.SwiftBrowse, PUP/Win32.BrowseFox
Antiy-AVLGrayWare[AdWare:not-a-virus]/Win32.Yotoon.bfm, GrayWare[NetTool:not-a-virus]/Win64.NetFilter.a
AvastWin32:Adware-BYZ [PUP], Win32:BrowseFox-EE [PUP]
AviraADWARE/BrowseFox.Gen7, Adware/BrowseFox.A.15, Adware/BrowseFox.A.282
Baidu-InternationalAdware.Win32.BrowseFox.bH, Adware.Win32.BrowseFox.whil, Adware.Win32.BrowseFox.V
BitDefenderGen:Variant.Adware.SwiftBrowse.1, Adware.NetFilter.E, Adware.NetFilter.J, Adware.BrowseFox.AT, Adware.SwiftBrowse.CH
BkavW64.HfsAdware.5637, W32.BrowseFoxJ.Adware
CAT-QuickHealAdWare.Yotoon.A5
ClamAVWin.Adware.Agent-22685, Win.Adware.Netfilter-130, Win.Adware.Swiftbrowse-497
ComodoApplication.Win32.BrowseFox.B, TrojWare.Win32.AltBrowse.IZZV
CyrenW64/A-59c9c70a!Eldorado, W32/S-bc825f4f!Eldorado
DrWebAdware.Plugin.100, Trojan.BPlug.437, Trojan.BPlug.10, Trojan.BPlug.123, Trojan.Yontoo.1734
ESET-NOD32a variant of MSIL/BrowseFox.A, Win32/BrowseFox.V, a variant of Win32/BrowseFox.G, a variant of Win32/BrowseFox.H, a variant of Win64/NetFilter.A potentially unsafe
EmsisoftAdware.NetFilter.E (B), Adware.BrowseFox.AT (B), Adware.SwiftBrowse.CH (B)
F-ProtW32/A-de841313!Eldorado, W64/A-a8e2f748!Eldorado, W32/A-b3b70cb0!Eldorado, W64/A-59c9c70a!Eldorado, W32/S-bc825f4f!Eldorado
F-SecureGen:Variant.Adware.SwiftBrowse.1, Adware.NetFilter.E, Adware.NetFilter.J, Adware.BrowseFox.AT, Adware.SwiftBrowse.CH
FortinetRiskware/BrowseFox
GDataGen:Variant.Adware.SwiftBrowse.1, Adware.NetFilter.E, Adware.NetFilter.J, Adware.BrowseFox.AT, Adware.SwiftBrowse.CH
Ikarusnot-a-virus:AdWare.Yotoon, AdWare.SwiftBrowse
JiangminAdWare/Yotoon.m, AdWare/Yotoon.ap
K7AntiVirusTrojan ( 004af26b1 ), Adware ( 0040f9f21 )
K7GWTrojan ( 004af26b1 ), Adware ( 0040f9f21 )
Kasperskynot-a-virus:AdWare.Win32.Yotoon.bfm
KingsoftWin32.Troj.Generic.a.(kcloud)
MalwarebytesPUP.Optional.Whilokii.A, PUP.Optional.SwiftBrowse
McAfeeArtemis!BAD42B9D0F36, Artemis!F98C22D9BFBB, BrowseFox-FTR, Artemis!7F3EB520D263
McAfee-GW-EditionArtemis!BAD42B9D0F36, Artemis!F98C22D9BFBB, BrowseFox-FTR, BehavesLike.Win64.PUPAmonetize.ph, Artemis
MicroWorld-eScanGen:Variant.Adware.SwiftBrowse.1, Adware.NetFilter.E, Adware.NetFilter.J, Adware.BrowseFox.AT, Adware.SwiftBrowse.CH
NANO-AntivirusRiskware.Win32.Kranet.dgiwfc, Riskware.Win32.NetFilter.dgqvkd, Riskware.Win32.Yotoon.denstu, Riskware.Win32.BPlug.djpkri
PandaTrj/CI.A
Qihoo-360Win32/Virus.Adware.eb6
SUPERAntiSpywareAdware.SwiftBrowse, Adware.BrowseFox/Variant
SophosBrowse Fox, BrowseSmart
SymantecYontoo.C
TrendMicro-HouseCallTROJ_GEN.F47V0927, TROJ_GEN.F47V0930, TROJ_GEN.F47V0116, TROJ_GEN.F47V0602
VBA32AdWare.Yotoon
VIPREYontoo (fs), Trojan.Win32.Generic!BT
ZillyaAdware.Kranet.Win32.476, Adware.Yotoon.Win64.10, Adware.Yotoon.Win64.6, Adware.Yotoon.Win64.14
nProtectAdware.NetFilter.E, Adware.NetFilter.J, Trojan-Clicker/W32.Yotoon.123672, Adware.SwiftBrowse.CH

* How the Detection Percentage is Calculated

The detection percentage is based on that I've collected 930 scan reports for the Whilokii files. 219 of these scan results came up with some sort of detection. You can view the full details of the scan reports by examining the files listed above.

Analysis Details

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

Comments

No comments posted yet.

Leave a reply