search

TheSpeedX / TBomb

This is a SMS And Call Bomber For Linux And Termux
Other
4.35k stars 1.58k forks source link

SMS bombing not working after update #145

Closed lavish440 closed 3 years ago

lavish440 commented 4 years ago

The script says it sent 10 SMS but the victim receives only 1 or 2.

0n1cOn3 commented 4 years ago

Due misusing of TBomb, several API's died. Don't be afraid if you don't see all send messages.

lavish440 commented 4 years ago

Most of the times no message is sent. Everything worked fine with version 2.0. This only started happening after the devs downgraded the tool.

0n1cOn3 commented 4 years ago

You can say @scpketer @darkestentropy thank you. Before the bomber.py has been deobfuscated, all API's worked like a charm. SpeedX told then more then once, bomber.py must be encrypted or the API's gonna diying.

And those two guys forced him for decrypt that and here we are today. After a year, TBomb is almost dead...

ghost commented 4 years ago

just as planned, @0n1cOn3 :P

0n1cOn3 commented 4 years ago

You know what i mean ;-)

ghost commented 4 years ago

Nope, I don't think so.

0n1cOn3 commented 4 years ago

TBomb was never injected with a bad code. Just decrypted due the misuse of the APIs. Now we have the salat 😅

ghost commented 4 years ago

I never stated the otherwise, pal.

Besides, API endpoints are extremely subject to change, so don't blame it on us.

0n1cOn3 commented 4 years ago

I never stated the otherwise, pal.

Besides, API endpoints are extremely subject to change, so don't blame it on us.

Well, SpeedX explained why bomber.py was encrypted...

And you did kinda someting like that ;-) See #19

ghost commented 4 years ago

>SpeedX explained why bomber.py was encrypted...

For your information, API endpoints can't tell whether their malicious usage was initiated by TBomb or any other application alike. Of course, they can determine whether that usage is malicious or not in the first place, but then it's unaffected by TBomb's being open-source or not.

I highly doubt that any of the API providers even acknowledge that they were used particularly by the TBomb.

0n1cOn3 commented 4 years ago

For your information, API endpoints can't tell whether their malicious usage was initiated by TBomb or any other application alike. Of course, they can determine whether that usage is malicious or not in the first place, but then it's unaffected by TBomb's being open-source or not.

We are not specifically concerned with API validation here, but with the release of bomber.py (TBomb) as an open source file itself. And the warning that TBomb is being abused was mentioned several times in those days.

Now we are so far that this project has a large audience, but is no longer useful for anything.

I see so many projects on Github where the files are already precompiled. And there is no fuss about the source code.

So I can't understand why you pushed SpeedX until he MUST release it decrypted. As you can see for yourself, there are many requests about "the application is not working

ghost commented 4 years ago

Reconsider my 'just as planned' once again, boy.

0n1cOn3 commented 4 years ago

Reconsider my 'just as planned' once again, boy.

I do not understand

ghost commented 4 years ago

>Oh noes, TBomb is dead after a year >Just as planned.

Once. Again.

ghost commented 4 years ago

Leaving now, contact via Telegram/E-mail, I'm outta here.

TheSpeedX commented 3 years ago

The code has been updated and this issue serves no further purpose.