Marcos

If the Fynloski malware is not found even with the latest signature database 8529, try performing one more scan with 8530 which will have detection for recent new Fynloski variants included. Should it still be detected only during a memory scan, create a SysInspector log and submit it to ESET along with a link to this thread as per the instructions here.

Unfortunately, this is the only possible workaround. Excluding files just by names regardless of the path is dangerous as malware could use that name to evade detection.

Why not use automatic mode with exceptions if you are not sure whether to allow or deny certain communication in interactive mode?

The website will be unblocked in the next update. As mentioned by Janus, the best practice for reporting FPs is by following the instructions in the aforementioned KB article.

Please contact Customer care and supply them the ERA server log as well as the screen shot of the error.

Please submit the SysInspector log along with a description of the issue to ESET as per the instructions here.

If you temporarily enable logging of blocked operations in the advanced HIPS setup, are certain block events logged?

I wrote in another thread that V7 beta currently doesn't support Windows 8.1 PR. It will be supported in the next beta build.

I assume that no communication was blocked, but just in case enable logging of blocked communications in the IDS setup, reproduce the problem and then check the firewall log if there are any records about blocked communications / connections. If there are some, post the records here.

The website is not blocked. Please send a screen shot of the alert you're getting to ESET as per the instructions here.

The websites will be unblocked as of the next update. Feel free to report them to ESET as per the instructions here in the future.

This is a known issue and will be addressed in the next beta build.

Hello, you can send me a personal message which I will pass to the engineers.

There is no difference between these applications except the way they activate.

We have launched a full investigation on how the incident occurred and will share more information soon, as it will be completed. As well we were tracing the origins of the attack and were able to shutdown the website that the criminal has been using and the fake form has been removed. We have notified German users about the fake e-mail via special e-mail message and the broader German public via our website and social media. We advised people who might have filled out the fake form with sensitive financial data to contact their financial institution immediately. We are still continuing our investigation and are gathering important information to notify the affected.

Have you tried booting to Windows Recovery Console and running "Bootrec /fixmbr" and "Bootrec /fixboot"? After booting to Windows, please provide us with the following logs: - Sirefef cleaner log (should have been created as it was cleaning the malware) - SysInspector log - ESET Threat log / On-demand scanner log details if the threat was previously detected When done, compress the logs, upload the archive to a safe location and PM me the download link.

Since we were unable to reproduce the issue, I wonder if other users who have encountered the issue could report it here.

ESET USSD Control has been included in EMS since Nov 2012.

You can adjust the policy used so that whenever clients connect to ERAS, they'll always download the desired configuration (policy). If you want to keep existing configurations and don't want to use a policy, simply push a configuration with the desired setting marked to clients.

V7 beta is currently not compatible with Windows 8.1. The next beta build will fully support it.

Do you have communication for bridged connections allowed in the IDS setup? Also try enabling the "Maintain inactive TCP connections" option.

Most likely they are malicious executables with a folder icon and the name of the original files while the original files are hidden. Try to view the flashdrive content with the display of hidden and system files enabled.

Is the threat detected by ESET ? Please create a SysInspector log and submit it along with the "Detected threats" log and a link to this thread to ESET as per the instructions here.

This is a known v7 issue with Windows 8.1 which will be addressed in the next beta build.

This just started happening to me too, very annoying, can this be fixed? Please make a video demonstrating the issue and post the link to it here then.