I quite agree - spamming an advert on a forum does not sit well with with me either. It stinks of desperation. People who run spam bots or post spam generally go hand in hand with the people who run malicious websites, phishing scams, etc. These are the very type people they're supposedly trying to protect us from with their security applications. As such, I'm also suspicious, and I certainly don't endorse or promote any of their products. Nor do I agree with advertising applications through spamming like this - we have an apps forum specifically for developers to promote their applications. We also have an apps directory, and application support forums for developers to help their users.
However, I did find the stuff on the page they linked interesting. I've worked in the area of internet security for several years, so it caught my attention and seems genuine.
If you want to know how the SMS vulnerability was found (it affects iPhone, Android, and WinMo if I remember correctly), you can read the research paper on it here: http://www.blackhat.com/presentations/bh-usa-09/MILLER/BHUSA09-Miller-FuzzingPhone-PAPER.pdf
In short though, the researchers added an injector layer above the bottom of the telephony stack which allowed them to intercept and inject information between the modem and multiplexor. Thus they could send/receive anything between the two a bit like a man-in-the-middle attack, and simulating the sending/receiving of SMS messages without actually sending any (and costing them money). Once you have that in place you can send random data, millions of times a second, and see what happens. Eventually unexpected data like that causes something abnormal to happen. You can then study this.
Have a look at section 6.2 in that PDF I linked... it says:
I don't even know if it's fixed on the iPhone... According to one website which mentions this exploit, "Apple did not respond to a request to confirm reports that it is working on a fix for the iPhone vulnerabilities. Google confirmed that the Android issue has been patched.".
I know that this was patched in Android 1.6, but I don't know which release/patch of it (the UK, for example, got 1.6 then a security patch later).