itman

Are you receiving this notification? Network Event Blocked. Duplicate IP on Network. A Computer (169.254.1.1) on the network is sending malicious traffic. This can be an attempt to attack your computer. Remote address: 169.254.1.1. Continue Blocking / Allow

Only Eset Admins cab read forum attachments. This screen shot of the alert doesn't help since since it doesn't show the "file" that contains the malware. Open Eset Detection log. Right mouse click on the entry created for this Eset alert. Select "Copy" which will save the entry to the desktop clipboard. Now reply in this forum thread and paste the clipboard entry in the reply.

No. You should have received the key in an e-mail from whomever you purchased it from. If you purchased a boxed version of Eset, the key is shown on an insert within the CD case. Otherwise, post your Eset public license ID as shown below and hopefully @Marcos can PM you your license key

That license I assume has been de-activated by Eset Russia since it has been "leaked." You will have to purchase a new license from https://www.eset.com/it/home-store/ . What is strange is when I connect to this web site, I will receive a 404 error from FireFox after a period of time. Perhaps because I am trying to do so from the U.S.?

Do you know what your existing Eset license key is? If so when you reinstall Eset, you can use that key to activate Eset.

Upload to free file sharing web site and PM @Marcos the download link for the file.

I also was thinking along this line; a hacked version of Eset somehow got installed. I had something like this happen years back when I was using Emsisoft. Somehow a hacked version of it got installed on Win 7 I was using at the time. And the hack was insidious to say the least. Only critical components were replaced like the engine component. I could never fully establish how this happened, but my best guess was I somehow received a hacked EAM product update. If the OP is using Win 10 Home version, rule out RDP since its not installed (inbound RDP) on the Home versions.

Scroll down to the section titled "Installing .CAB driver package" in this article: https://www.winhelponline.com/blog/install-cab-msu-updates-mu-catalog/

There is also another way you can get your money refunded. Assumed is you used a credit card for the Russian Eset license purchase. I don't know what card you used or what card issuer policies in Italy are. In the U.S. and with the major card issuers; e.g. Visa, MasterCard, etc., you can dispute the transaction. Clearly not receiving the product you purchased falls under disputed transaction criteria. The only requirement is you first try to resolve the issue yourself which you have fulfilled. There are a couple of "glitches" though you will have to verify. First, this was an interna

This is B.S. All they have to do to is deactivate the license key. I would escalate the issue to Eset corporate in Slovakia. The problem here is well .......... hard to believe since nothing like this has been documented to date as far as I am aware of. The problem here is you never reported previous the "mysterious" Eset GUI change to Russian.

FYI: https://www.infosecurity-magazine.com/news/29-vpn-services-owned-by-six/ This is the actual article by VPNpro which gets into the real "nitty gritty": https://vpnpro.com/blog/hidden-vpn-owners-unveiled-97-vpns-23-companies/ . The above InfoSecurity article is just a summary.

BTW - here's the full "nitty gritty" on QUIC: https://datatracker.ietf.org/doc/draft-ietf-quic-transport/?include_text=1 Also, this standard is not yet officially approved. Additionally, everything I have read about QUIC indicates that these security concern articles about it are unfounded.

The only way this could happen that I can think of is somehow a borked ; i.e. Russian language, Eset update was downloaded to your PC. If this happened, it would be a "first" as far as I am aware of.

Technically speaking that is not possible without first uninstalling Eset and reinstalling it: https://support.eset.com/en/kb3552-change-the-language-of-your-eset-windows-home-product .

Did you perform this procedure? https://support.eset.com/en/kb2711-eset-mobile-security-for-android-faq