We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

ابحث في الدعم

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

This thread was closed and archived. Please ask a new question if you need help.

Firefox tries to open https://p2.dntrax.com on startup

  • 3 ردود
  • 23 have this problem
  • 9 views
  • آخر ردّ كتبه MartynWheeler

more options

Since the last update, according to Avast, Firefox tries to open the malicious url https://p2.dntrax.com on startup. Is this a false positive, or is there something wrong that I need to fix?

(The startup page is my home page, a simple non-scripted plain html file that resides on the hard drive. This has not changed in years.)

Since the last update, according to Avast, Firefox tries to open the malicious url https://p2.dntrax.com on startup. Is this a false positive, or is there something wrong that I need to fix? (The startup page is my home page, a simple non-scripted plain html file that resides on the hard drive. This has not changed in years.)

الحل المُختار

You are absolutely correct, IE Tab Plus 2.0.0.0 is the culprit. The warning appears/does not appear depending on whether it is enabled or not.

Thanks!

Read this answer in context 👍 9

All Replies (3)

more options

That seems to be some kind of advertising service. Can you get the full URL? Sometimes one of the parameters will link it to an add-on or other program.

How long have you had the "IE Tab Plus 2.0.0.0" extension? Some versions of "IE Tab Plus" may include unwanted advertising or search features.

more options

That is the full URL reported by Avast.

I've had all these add-ins and extensions for a long time. I haven't used IE Tab in a very long time, though, I could deactivate it.

more options

الحل المُختار

You are absolutely correct, IE Tab Plus 2.0.0.0 is the culprit. The warning appears/does not appear depending on whether it is enabled or not.

Thanks!