FP (or F/P) means False Positive... a SAFE file, which Avast is erronesly detecting as being a virus.
If you have EXACTLY the same file/version being detected on your system, I'd say you're safe [as I believe I am]. If you're saying you have something "similar"... or perhaps ANOTHER file being detected as Sirefef... I can't make any such assertion.
Officially, we have to wait for avast to concur... to see if they adjust their database to no longer detect this file in the future. When/if they do, i'll report back here.
« Last Edit: June 30, 2012, 03:08:10 AM by ky331 »
Lenovo T530 laptop, Intel Core i5-3320M @ 2.60 GHz, 8GB RAM, Windows 7 Pro SP1 (64-bit), avast! v2016 Free, MBAM2 Pro, Windows Firewall, MVPS HOSTS file, OpenDNS Family Shield, Zemana AntiLogger Free, SpywareBlaster, IE11 & Firefox [both using WOT (IE set to WARN, FF set to BLOCK)], WinPatrol PLUS, MBAE, MCShield, CryptoPrevent, SAS (on-demand scanner), Secunia PSI.
[I believe computer-users who sandbox (Sandboxie) are acting prudently.]