Etisalat BlackBerry update was indeed spyware, RIM provides a solution
by Darren Murph 
posted Jul 21st 2009 @ 9:41AM
"Etisalat appears to have distributed a telecommunications surveillance application... independent sources have concluded that it is possible that the installed software could then enable unauthorized access to private or confidential information stored on the user's smartphone. Independent sources have concluded that the Etisalat update is not designed to improve performance of your BlackBerry Handheld, but rather to send received messages back to a central server."
Like we said, yikes. The zaniest part is that Etisalat isn't backing down, still assuring the world that the upgrades were "required for service enhancements." At any rate, RIM has made remarkably clear that the update wasn't one authorized by the company, and it's even providing an app remover for those who'd prefer their BlackBerry to be in working order and, you know, not forwarding all their email to some dude in an Etisalat supply closet. Good on you, RIM. Bad on you, Etisalat.
[Thanks, Gerald]
Read - Confirmation of spyware
Read - RIM app remover
In 2005, Greek authorities discovered a plot hatched and executed by unknown sources which allowed the tapping of wireless phones on the Vodafone network belonging to the country's Prime Minister and other top officials, making it one of the furthest reaching covert infiltrations of a government in history. A recent report from IEEE Spectrum shows that the tap was made possible by a 6,500 line piece of code called a rootkit, the first-ever to be embedded in a phone switch's OS. The complex hack took advantage of aging phone systems by disabling transaction logs on calls and allowing call monitoring on four switches within the teleco's computers, thus sending the call to another phone for monitoring (similar to a legal wiretap). The spies covered their tracks by creating patches on the system which routed the calls around logging software which would have alerted admins, and were only discovered when they tried to update their software. The case clearly exposes holes in call security amongst providers (due largely in part to outdated systems), and suggests the possibility that this kind of thing could easily happen again... to you!
