Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Got 2 Trojan coin hiva.a virus by using firefox

  • 4 replies
  • 1 has this problem
  • 1 view
  • Last reply by TyDraniu

more options

I had experience [this](https://support.mozilla.org/en-US/questions/1236971) problem last year in the month of October. Now i get this again.This time i have 2 Trojan viruses in my cache.Now what has Firefox done to eliminate this problem.Can't this problem be eliminated altogether. I have gone through this but its just a temporary solution.I don't wan't Trojan's in my cache to creep in altogether.

I had experience [this](https://support.mozilla.org/en-US/questions/1236971) problem last year in the month of October. Now i get this again.This time i have 2 Trojan viruses in my cache.Now what has Firefox done to eliminate this problem.Can't this problem be eliminated altogether. I have gone through this but its just a temporary solution.I don't wan't Trojan's in my cache to creep in altogether.

Chosen solution

My reply from that thread:

You are Not infected with a Trojan as it will either get overwritten over time as Cache gets used or deleted if you manually clear the Cache in Firefox.

This may be a older article but it still applies = Firefox cache file was infected with a virus

Read this answer in context 👍 0

All Replies (4)

more options

this is the below image

more options
  1. Install the ublock Origin addon.
  2. Import this list into your adblocker.
more options

Chosen Solution

My reply from that thread:

You are Not infected with a Trojan as it will either get overwritten over time as Cache gets used or deleted if you manually clear the Cache in Firefox.

This may be a older article but it still applies = Firefox cache file was infected with a virus

Modified by James

more options

Go to about:config and set privacy.trackingprotection.cryptomining.enabled = true.

See bug 1519101.