Did you just find a download or a file on your computer that has a digital signature from Laflurla? Some of the security products refers to the detected files as PUP.Optional.Laflurla.A and Adware.BrowseFox/Variant. The detection rate for the Laflurla files collected here is 17%. Please read on for more details.
You'll probably notice Laflurla 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:

You can view the additional details from the Laflurla digital signature with the following steps:
Here is a screenshot of a file that has been digitally signed by Laflurla:

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 Laflurla and that the file has not been tampered with.
If you click the View Certificate button shown in the screencap 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 Laflurla, such as the street name, city and country.
VeriSign Class 3 Code Signing 2010 CA has issued the Laflurla certificates. You can also view the details of the issuer by clicking the View Certificate button shown in the screencap above.
The following are the Laflurla files I have gathered, thanks to the FreeFixer users.
| Detection Ratio | File Name |
|---|---|
| 5/50 | updateLaflurla.exe |
| 18/51 | Laflurlabho.dll |
| 2/53 | {6b320d34-648f-46d8-8353-a4300db1c49c}gw.sys |
| 3/51 | updateLaflurla.exe |
| 17/51 | Laflurlabho.dll |
| 3/51 | Laflurla.BrowserFilter.Helper.dll |
| 10/51 | Laflurlabho.dll |
| 3/50 | updatelaflurla.exe |
| 22/51 | Laflurlabho.dll |
| 23/51 | Setup[1].exe |
| 27/52 | Laflurlabho.dll |
| 10/55 | utilLaflurla.exe |
Here's the detection names for the Laflurla files. I've grouped the detection names by each scanner engine. Thanks to VirusTotal for the scan results.
| Scanner | Detection Names |
|---|---|
| AVG | Generic.DE2, MalSign.Generic.DE2, BrowseFox.F |
| AVware | Yontoo (fs) |
| Agnitum | Riskware.Agent!, PUA.Agent! |
| AntiVir | APPL/BrowseFox.Gen2, APPL/BrowseFox.Gen |
| Antiy-AVL | GrayWare[AdWare:not-a-virus]/Win32.Agent, GrayWare[AdWare:not-a-virus]/Win32.LinkSwift |
| Baidu-International | Adware.Win32.Agent.afpU, Adware.Win32.BrowseFox.BH |
| Comodo | Application.Win32.Altbrowse.AK |
| DrWeb | Trojan.BPlug.35, Trojan.BPlug.28, Trojan.BPlug.37, Trojan.BPlug.137 |
| ESET-NOD32 | a variant of Win32/BrowseFox.H, a variant of Win32/BrowseFox.F |
| Fortinet | Adware/Agent |
| GData | Win32.Application.BrowseFox.B |
| Ikarus | not-a-virus:AdWare.Win32.Agent, PUA.BrowseFox |
| Jiangmin | Adware/Agent.izz, AdWare/LinkSwift.f |
| K7AntiVirus | Unwanted-Program ( 00454f261 ) |
| K7GW | Unwanted-Program ( 00454f261 ) |
| Kaspersky | not-a-virus:AdWare.Win32.Agent.ahbx |
| Kingsoft | Win32.Troj.Agent.ah.(kcloud), VIRUS_UNKNOWN |
| Malwarebytes | PUP.Optional.Laflurla.A |
| McAfee | Artemis!B43DDCFE3BD0, Artemis!F62724D15C37, Artemis!6BE3160E3F01, Artemis!E55D1F67B115, Artemis!C8E20D72B366 |
| McAfee-GW-Edition | Artemis!B43DDCFE3BD0, Artemis!F62724D15C37, Artemis!6BE3160E3F01, Artemis!C8E20D72B366 |
| NANO-Antivirus | Riskware.Win32.Agent.cuenda |
| Rising | NS:PUF.SilenceInstaller!1.9DDF |
| SUPERAntiSpyware | Adware.BrowseFox/Variant |
| Sophos | Generic PUA IG, Generic PUA FJ, Generic PUA DK, Generic PUA GL, Generic PUA BA |
| Symantec | Trojan.ADH.2 |
| TrendMicro-HouseCall | TROJ_GEN.F47V0320, TROJ_GEN.F47V0408, TROJ_GEN.F47V0322, TROJ_GEN.F47V0402, TROJ_GEN.F47V0319, TROJ_GE.2BA6B97D |
| VBA32 | AdWare.Agent.aiwa, AdWare.Agent |
| VIPRE | Yontoo (fs), Trojan.Win32.Generic!BT |
| Zillya | Adware.Agent.Win32.9009 |
| nProtect | Trojan-Clicker/W32.Agent.323360.G |
The detection percentage is based on that I have collected 820 scan results for the Laflurla files. 143 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 has been done on certificates with the following serial numbers: