Did you just stumble upon a download or a file on your computer that is digitally signed by App Bud? Some of the security products refers to the detected files as Adware.Agent.OHP and Gen:Variant.Adware.SwiftBrowse.1. The detection rate for the App Bud files collected here is 43%. Please read on for more details.
You will probably see App Bud when double-clicking to run the file. The publisher name shows up as the "Verified publisher" in the UAC dialog as the screenshot shows:

You can view the additional details from the App Bud digital signature with the following steps:
Here's a screencap of a file that has been signed by App Bud:

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 App Bud and that the file has not been tampered with.
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 see the address for App Bud, such as the street name, city and country.
VeriSign Class 3 Code Signing 2010 CA has issued the App Bud certificates. You can also examine the details of the issuer by clicking the View Certificate button shown in the screengrab above.
The following are the App Bud files I have gathered, thanks to the FreeFixer users.
| Detection Ratio | File Name |
|---|---|
| 18/53 | maintainer.exe |
| 13/54 | AppBudbho.dll |
| 39/56 | {e6ca9971-30ed-444a-9489-82fca50b2062}gw64.sys |
Here's the detection names for the App Bud files. I have grouped the detection names by each scanner engine. Thanks to VirusTotal for the scan results.
| Scanner | Detection Names |
|---|---|
| ALYac | Adware.Agent.OHP |
| AVG | Generic.1E1, BrowseFox.F |
| AVware | Yontoo (fs), Trojan.Win32.Generic!BT |
| Ad-Aware | Gen:Variant.Adware.SwiftBrowse.1, Adware.Agent.OHP |
| Agnitum | Trojan.BPlug! |
| AhnLab-V3 | Adware/Win32.SwiftBrowse, Adware/Win32.BHO, Trojan/Win64.SwiftBrowse |
| AntiVir | APPL/BrowseFox.Gen2 |
| Antiy-AVL | GrayWare[AdWare:not-a-virus]/Win32.Kranet, Trojan/Win32.TSGeneric |
| Arcabit | Adware.Agent.OHP |
| Avast | Win32:PUP-gen [PUP], Win32:BrowseFox-EG [PUP] |
| Baidu-International | Adware.Win32.BrowseFox.bV, Adware.Win32.BrowseFox.bO, Adware.Win64.BrowseFox.A |
| BitDefender | Gen:Variant.Adware.SwiftBrowse.1, Adware.Agent.OHP |
| ClamAV | Win.Adware.Agent-22685, Win.Adware.Swiftbrowse-75 |
| Comodo | UnclassifiedMalware |
| Cyren | W64/A-e967bae2!Eldorado |
| DrWeb | Trojan.BPlug.281, Trojan.BPlug.143, Trojan.Yontoo.1734 |
| ESET-NOD32 | Win32/BrowseFox.V, Win64/Riskware.NetFilter.A |
| Emsisoft | Gen:Variant.Adware.SwiftBrowse.1 (B), Adware.Agent.OHP (B) |
| F-Prot | W64/A-e967bae2!Eldorado |
| F-Secure | Gen:Variant.Adware.SwiftBrowse.1, Adware.Agent.OHP |
| Fortinet | Riskware/BrowseFox |
| GData | Gen:Variant.Adware.SwiftBrowse.1, Adware.Agent.OHP |
| Ikarus | AdWare.BrowseFox, AdWare.SpadeCast |
| Jiangmin | AdWare/Yotoon.m |
| Malwarebytes | PUP.Optional.AppBud.A, PUP.Optional.BrowseFox |
| McAfee | Artemis!4C08F1CA9CB7, RDN/Generic PUP.x!cnl |
| McAfee-GW-Edition | Artemis!4C08F1CA9CB7, RDN/Generic PUP.x!cnl |
| MicroWorld-eScan | Gen:Variant.Adware.SwiftBrowse.1, Adware.Agent.OHP |
| NANO-Antivirus | Riskware.Win32.Kranet.dgiwfc, Trojan.Win64.Yontoo.dtmepz |
| Panda | Generic Suspicious |
| Rising | PE:Adware.BrowserFox!1.A127 [F] |
| SUPERAntiSpyware | Adware.NetFilter/Variant |
| Sophos | BrowseSmart (PUA) |
| Symantec | PUA.Yontoo.C |
| Tencent | Win64.Risk.Riskware.Amwc |
| TrendMicro | TROJ_SPNV.03IJ14 |
| TrendMicro-HouseCall | PUA_BROWSEFOX |
| VBA32 | AdWare.Kranet |
| VIPRE | Yontoo (fs), Trojan.Win32.Generic!BT |
| ViRobot | Trojan.Win32.S.Agent.61064.B[h] |
| Zillya | Adware.Kranet.Win32.476, Adware.Yotoon.Win64.3 |
| nProtect | Adware.Agent.OHP |
The detection percentage is based on that I have gathered 163 scan reports for the App Bud files. 70 of these scan reports 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.
The analysis is done on certificates with the following serial numbers: