3GM Updates

[Tivon]

"Just letting you know that I am updating Joomla so be on the lookout for issues if they pop up." ~Zach Jeffers

Just thought everyone would like to know. There are some good reasons for this right now. Might be a good idea for everyone to run a virus scan on your computers and particularly scan for "Trojan-Downloader.JS.Agent.yd" Also known as a "Winblows virus".

*Update* Also scan for "malware Exploit.Win32.IMG-ANI.ak". Forum might also have problems now. Zach is on the move to fix these problems ASAP!

[GraysonPeddie]

Even with Vista x64, with User Account Control turned on, right?

[Amdboy89]

I guess thats why my McAffee has been going crazy the last few times I've been in this site. I was going to ask why my VS keeps alerting me of all these viruses but I guess this answers it
Thanks for the hands up Tivon!!!

[Manic Mouse]

My Kaspersky firewall caught one of these coming from here. I blocked it.

[egarrard]

NOD 32 caught several things too. Glad to know it was a failure of some sort on here rather than my system.

[Nodspy]

Was wondering why nod32 wouldn't shut up.

[robodude666]

Huh, interesting. I haven't gotten a single complaint from AVG. Could it be that I have Adblock Plus on?

[eire1274]

It's nice when your active network protects you before your antivirus even has any idea what's going on... :spin

[Happy Camper]

^^^^

That may be why I haven't got so much of a peep out of Avira. I'm running a scan anyway but normally that's pretty good at picking things up.

At what times was the site vulnerable?

[Tivon]

Avast and AVG didn't pickup anything. So far Kaspersky has detected the problems. I'm using the free scan at work and home, so far nothing is turning up on my end. :)

[egarrard]

All this brings up a question. If your AV program found something and blocked it, then you scanned your system and it found nothing, can you REALLY trust it? I just don't want my system screwed up enough for Windows to have to try and "repair" it. That's always the kiss of death.

[Tivon]

At this point we think it could of been a botnet that scanned for files with write access, then applied a frame of sorts and that's what happened. There was some files left open from the old website that Zach didn't have time to clean up till now. We all checked our computers to be sure we didn't spread those Trojans, but you know the drill, better safe than sorry.