NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Antivirus scanner found a threat (Unix.Trojan.Mirai-5607459-1) in the file /bin/busybox
6.6.1 on board and just did a fresh install for a new deployment, new drives. Went ahead and enabled AV, and almost immediately got this warning. Antivirus scanner found a threat (Unix.Trojan.Mir...
jtowntex wrote:
Same deal, I have had a lot of trouble since the upgrade to 6.6.1 and then today...
Same deal, I have had a lot of trouble since the upgrade to 6.6.1 and then today...
Antivirus scanner found a threat (Unix.Trojan.Mirai-5607459-1) in the file /bin/busybox. Please delete the infected file soon if automatic delete setting is not enabled.
jtowntex wrote:
Same deal, I have had a lot of trouble since the upgrade to 6.6.1 and then today...
Awesome.
Thanks for all the effort on this everyone. These upgrades were a long time coming I think. I'm glad they're conquering it. It's a shame it didn't go smoother but happily we've got a decent community here to help out those unfortunate ones like us.
OK... so that linked article explains why they limited the size of the scanned files too. Using /tmp as ClamAV workspace. I'm hoping they move it to /data/.clamav or something. :) For now, it's AV off state again for a while.
It's curious, too, that I've seen no evidence of this issue on my 528 (16gb RAM) but am seeing it on a Pro6 (8gb RAM). I don't believe the root filesystems are any different between them, though the CPU is of course less (not Atom or ARM though). Anywho, it'll be interesting to see how it unfolds. It was certainly doing better overall than the previous solution, until this issue cropped up.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
