Did you just run into a download or a file on your computer that has a digital signature from grassmow? Some of the security products refers to the detected files as Adware.SwiftBrowse.CH and Trojan.Win32.Generic!BT. The detection rate for the grassmow files collected here is 40%. Please read on for more details.
You will typically notice grassmow when clicking to run the file. The publisher name is displayed as the "Verified publisher" in the UAC dialog as the screenshot shows:

You can view the additional details from the grassmow digital signature with the following steps:
Here's a screenshot of a file signed by grassmow:

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 grassmow and that the file has not been tampered with.
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 grassmow, such as the street name, city and country.
VeriSign Class 3 Code Signing 2010 CA has issued the grassmow certificates. You can also examine the details of the issuer by clicking the View Certificate button shown in the screenshot above.
These are the grassmow files I have gathered, thanks to the FreeFixer users.
Here's the detection names for the grassmow files. I have grouped the detection names by each scanner engine. Thanks to VirusTotal for the scan results.
| Scanner | Detection Names |
|---|---|
| ALYac | Adware.SwiftBrowse.CH |
| AVG | Generic.D31 |
| AVware | Trojan.Win32.Generic!BT, Adware.BrowseFox |
| Ad-Aware | Adware.SwiftBrowse.BV, Adware.SwiftBrowse.CH |
| Agnitum | Riskware.NetFilter!, PUA.BrowseFox!, Riskware.Agent! |
| AhnLab-V3 | Trojan/Win64.SwiftBrowse |
| Antiy-AVL | GrayWare[NetTool:not-a-virus]/Win64.NetFilter.a |
| Avast | Win64:BrowseFox-C [PUP], MSIL:BrowseFox-R [PUP] |
| Avira | Adware/BrowseFox.A.1227, Adware/BrowseFox.aph, ADWARE/BrowseFox.aph |
| BitDefender | Adware.SwiftBrowse.BV, Adware.SwiftBrowse.CH |
| Bkav | W64.HfsAdware.54BD |
| ClamAV | Win.Adware.Swiftbrowse-284, Win.Adware.Netfilter-134, Win.Adware.Swiftbrowse-497 |
| Cyren | W64/A-59c9c70a!Eldorado |
| DrWeb | Tool.NetFilter.1, Tool.NetFilter.313, Trojan.Yontoo.1734 |
| ESET-NOD32 | a variant of Win64/BrowseFox.CD, a variant of Win64/BrowseFox.CG, a variant of Win64/BrowseFox.CD potentially unwanted, a variant of Win64/BrowseFox.CG potentially unwanted, a variant of Win64/NetFilter.A potentially unsafe |
| Emsisoft | Adware.SwiftBrowse.BV (B), Adware.SwiftBrowse.CH (B) |
| F-Prot | W64/A-abca7297!Eldorado, W32/A-248e95ab!Eldorado, W64/A-59c9c70a!Eldorado |
| F-Secure | Adware.SwiftBrowse.BV, Adware.SwiftBrowse.CH |
| Fortinet | Adware/BrowseFox, Adware/Komodia |
| GData | Adware.SwiftBrowse.BV, Adware.SwiftBrowse.CH |
| Ikarus | AdWare.BrowseFox |
| Jiangmin | AdWare/Yotoon.aq |
| K7AntiVirus | Adware ( 0040f9f21 ) |
| K7GW | Adware ( 0040f9f21 ) |
| Kaspersky | not-a-virus:NetTool.Win64.NetFilter.a |
| Kingsoft | Win32.Troj.Generic.a.(kcloud) |
| McAfee | Artemis!1504B58060D0, Artemis!95CAC9D2B13D, Artemis!706D3C14BE20, Artemis!2580C627495F |
| McAfee-GW-Edition | Artemis |
| MicroWorld-eScan | Adware.SwiftBrowse.BV, Adware.SwiftBrowse.CH |
| NANO-Antivirus | Riskware.Win32.NetFilter.dgkdox, Riskware.Win64.NetFilter.dljogx, Trojan.Win64.Yontoo.dpkyjg |
| Panda | Trj/CI.A |
| Qihoo-360 | Win32/Virus.Adware.145 |
| SUPERAntiSpyware | Adware.BrowseFox/Variant |
| Symantec | Trojan.Gen.2 |
| TrendMicro | TROJ_GEN.F0C2C00A515, HS_BROWSEFOX.SM, TROJ_GEN.R08NC0EC315 |
| TrendMicro-HouseCall | Suspicious_GEN.F47V1003, TROJ_GEN.F0C2C00A515, HS_BROWSEFOX.SM, TROJ_GEN.R08NC0EC315 |
| VBA32 | AdWare.Win64.Yotoon |
| VIPRE | Trojan.Win32.Generic!BT, Adware.BrowseFox |
| Zillya | Adware.Yotoon.Win64.13, Backdoor.CPEX.Win32.29350, Adware.Yotoon.Win64.14 |
| nProtect | Adware.SwiftBrowse.BV, Adware.SwiftBrowse.CH |
The detection percentage is based on the fact that I have gathered 500 scan reports for the grassmow files. 198 of these scan results came up with some sort of detection. If you like, you can view the full details of the scan results by examining the files listed above.
The analysis is done on certificates with the following serial numbers: