Researchers have uncovered Android 2.3 malware known as & GingerMaster,& which takes advantage of a jailbreak exploit to gain root access and execute instructions from a remote server. Meanwhile, McAfee Labs says malware developers are focusing on Android more than any other platform -- but adds that the number of actual threats found on smartphones in the wild remains small....
Quick question: Is there an effective way in place to report users rather than just simply reporting their posts? It seems that often these spam posters will come in and flood several subforums with spam, and rather than reporting each individual post (which I sort of remember mods saying somewhere was less than ideal for them), it might be better to be able to report a spam poster.
Australia’s financial, transactional and global IT security colossus, TrustDefender, warns that while 2010 was “the year of cybercrime”, 2011 will see the trend get worse – and more specific – as the “year of malware attacks”. Take cover!
Curtin University’s Anti-Spam Research Lab has calculated Spam 2.0 - found on blogs, wikis and social networks - could be costing large organisations $43,000 a year just to provide the additional storage capacity mopped up by Spam content. The Lab is now finalising patents which it hopes will allow the release of a new breed of anti-Spam tool later this year.
We offer a service that requires URLs from our domain to be linked to external URLs. About ten years ago, we discovered that this functionality can be abused by miscreants -- to link to malicious URLs.
Written by: Stephen Withers | Published in: SecurityAttacks on or using networked printers or multifunction devices are nothing new, but the growth in malware is affecting embedded systems including those used in such devices, according to Tom Moore, McAfee's vice president of embedded security.
We were recently made aware that our spam appliance was exhibiting the recent NTP monlist vulnerability. Since it is a spam appliance that was provided by a company we no longer do business with, our "temporary" fix was to put it behind a firewall to block UDP port 123. We are working on a replacement server.