Trojan Horse found

frank

frank

Suspended / Banned
Messages
2,498
Edit My Images
Yes
Avast tonight blocked the wife from logging into one of her catalogue companies showing as " HTML:iframe-QH" . She didn't put any personal details in and stopped what she was doing, I've discovered Avast users also Thomas Cook and John Lewis have been having the same problem.
Not sure if it is a false positive or not.
Anyone know if this might be connected to the problems Natwest is having or is it just Avast?
 
I've been getting a fair few warnings from avast recently, then revisit the page and all is clear.
Dunno if it's to do with them pusshing to go for the upgraded programme and trying rto scare people
 
I'm using the paid for version of Avast Internet Security
 
frank said:
Avast tonight blocked the wife from logging into one of her catalogue companies showing as " HTML:iframe-QH" . She didn't put any personal details in and stopped what she was doing, I've discovered Avast users also Thomas Cook and John Lewis have been having the same problem.
Not sure if it is a false positive or not.
Anyone know if this might be connected to the problems Natwest is having or is it just Avast?
Click to expand...

at what point on those sites did the warning come up?

http://www.thomascook.com/ appears to be down at the moment..
 
neil_g said:
at what point on those sites did the warning come up?
Click to expand...

Thomas Cook site as soon as entering site agree it seems down, other site was ISME http://www.isme.com/ on the home page clicking on the My Account from the list on the top right of page also brings up the exactly the same warning.

Reason I mentioned Natwest in first post is ISME payments can also be made via bank and they use Natwest, probably coincidence with the hassles they are having at the moment.

A full scan using Avast Internet Security then Malwarebytes shows no threats detected on my system.
 
Weird ! the above problem seems to be sorted now on the affected sites, ISME & Thomas Cook all working properly this morning, no trojan warnings.

wonder if it was wrong line of code in a Avast update causing the problem or it really was something on these two site, I guess it will be a state secret and we'll never know :shrug:
 
probably just something that made the page look like a generic iframe exploit, whether thats something new the sites put in that raised a false positive or avasts update had a new bit of info in for a new exploit that incorrectly detected those sites..

just one of those things. happens on all av software at some point.
 
You must log in or register to reply here.
Back
Top