PacFunction - 13% Detection Rate *

Did you just stumble upon a download or a file on your computer that has a digital signature from PacFunction? Some of the security products refers to the detected files as Adware.NetFilter.E and Pafun.E1F. The detection rate for the PacFunction files collected here is 13%. Please read on for more details.

You will probably notice PacFunction when running the file. The publisher name shows up as the "Verified publisher" in the UAC dialog as the screenshot shows:

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

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

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

Here's a screenshot of a file that has been signed by PacFunction:

Screenshot of the PacFunction certificate

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

If you click the View Certificate button shown in the screenshot 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, and so on. You can also see the address for PacFunction, such as the street name, city and country.

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

PacFunction Files

These are the PacFunction files I have collected, thanks to the FreeFixer users.

Detection RatioFile Name
16/49PacFunctionbho.dll
2/51updatePacFunction.exe
2/51XTLSApp.exe
3/51XTLSApp.exe
2/52{19854aff-7c07-4859-9831-cd028ac55dd0}gt.sys
4/52{19854aff-7c07-4859-9831-cd028ac55dd0}t.sys
4/51FilterApp_C64.exe
5/51FilterApp_C64.exe
11/50updatePacFunction.exe
5/53updatePacFunction.exe
9/54{19854aff-7c07-4859-9831-cd028ac55dd0}gt64.sys
9/54{19854aff-7c07-4859-9831-cd028ac55dd0}t64.sys
23/54wstlibg64.sys

Scanner and Detection Names

Here is the detection names for the PacFunction files. I have grouped the detection names by each scanner engine. Thanks to VirusTotal for the scan results.

ScannerDetection Names
ALYacAdware.NetFilter.E
AVGMalSign.Pafun.E1F, Pafun.E1F
AVwareTrojan.Win32.Generic!BT
Ad-AwareAdware.NetFilter.E
AgnitumPUA.Agent!, PUA.LinkSwift!, Trojan.BPlug!
AhnLab-V3Trojan/Win64.SwiftBrowse
Antiy-AVLGrayWare[AdWare:not-a-virus]/Win32.Agent, GrayWare[AdWare:not-a-virus]/Win32.LinkSwift
AvastMSIL:BrowseFox-N [PUP]
Baidu-InternationalAdware.Win32.BrowseFox.bH, Adware.Win32.BrowseFox.H, Adware.Win32.BrowseFox.BH
BitDefenderAdware.NetFilter.E
BkavW64.HfsAdware.1E08
ClamAVWin.Adware.Swiftbrowse-8, Win.Adware.Swiftbrowse-75
ComodoApplication.Win32.Altbrowse.AK
CyrenW64/A-e967bae2!Eldorado
DrWebTrojan.BPlug.28, Trojan.BPlug.35, Trojan.BPlug.123, Trojan.Yontoo.1778
ESET-NOD32a variant of Win32/BrowseFox.F, a variant of Win32/BrowseFox.H, a variant of Win32/BrowseFox.I, Win64/BrowseFox.A, a variant of Win64/NetFilter.A potentially unsafe
EmsisoftAdware.NetFilter.E (B)
F-ProtW64/A-7883d091!Eldorado, W64/A-e967bae2!Eldorado
F-SecureAdware.NetFilter.E
FortinetAdware/Agent, Riskware/BrowseFox
GDataAdware.NetFilter.E
Ikarusnot-a-virus:AdWare.Win32.Agent, AdWare.SwiftBrowse
JiangminAdware/Agent.jaw, AdWare/LinkSwift.bl, AdWare/Yotoon.m
KingsoftWin32.Troj.Agent.ah.(kcloud)
MalwarebytesPUP.Optional.PacFunction.A
McAfeeArtemis!AD088D7D8E54, Artemis!E5FCA88F0676
McAfee-GW-EditionArtemis!AD088D7D8E54, Artemis!E5FCA88F0676, BehavesLike.Win64.PUPAmonetize.qh
MicroWorld-eScanAdware.NetFilter.E
NANO-AntivirusRiskware.Win32.Agent.cqvnby, Trojan.Win32.CCM.cwxrgd
SUPERAntiSpywareAdware.NetFilter/Variant
SophosGeneric PUA KE, BrowseSmart
SymantecYontoo.C
TrendMicro-HouseCallTROJ_GEN.F47V0311, TROJ_GEN.F47V0422
VIPREYontoo (fs), Trojan.Win32.Generic!BT
ZillyaAdware.Yotoon.Win64.9
nProtectAdware.NetFilter.E

* How the Detection Percentage is Calculated

The detection percentage is based on that I have gathered 723 scan reports for the PacFunction files. 95 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 is done on certificates with the following serial numbers:

Comments

No comments posted yet.

Leave a reply