±Forensic Focus Partners

Become an advertising partner

±Your Account


Username
Password

Forgotten password/username?

Site Members:

New Today: 0 Overall: 36312
New Yesterday: 0 Visitors: 211

±Follow Forensic Focus

Forensic Focus Facebook PageForensic Focus on TwitterForensic Focus LinkedIn GroupForensic Focus YouTube Channel

RSS feeds: News Forums Articles

±Latest Articles

±Latest Videos

±Latest Jobs

UFED Cloud Analyzer and Telegram - beware!

Computer forensics discussion. Please ensure that your post is not better suited to one of the forums below (if it is, please post it there instead!)
Reply to topicReply to topic Printer Friendly Page
Forum FAQSearchView unanswered posts
 
  

ThePM
Senior Member
 

UFED Cloud Analyzer and Telegram - beware!

Post Posted: Aug 24, 18 15:06

My team did some testing last week with UFED Cloud Analyzer (latest version 7.3.2) to collect data from Telegram.

The collection did not give any error, but it only downloaded a couple of contacts and no messages.

Afterwards, we were unable to connect to the Telegram account. Turns out that we got the following error "Phone number is banned" Shocked

We tried connecting through the web interface, still unable and we still got the same error message.

We contacted Cellebrite about this. They said they would test and get back to us. It has been a week and still no feedback from them. They answer quicker than that usually if they are unable to replicate the issue...

So be careful guys if you want to use Cloud Analyzer to collect data from Telegram in a real case.

If I get any feedback from Cellebrite, I will post.  
 
  

ThePM
Senior Member
 

Re: UFED Cloud Analyzer and Telegram - beware!

Post Posted: Aug 28, 18 19:02

Following up on this topic,

Cellebrite was able to replicate the issue and their test Telegram account was also banned!

So, for now I guess we should stay away form Cloud Analyzer when dealing with Telegram.  
 
  

Kenobyte
Member
 

Re: UFED Cloud Analyzer and Telegram - beware!

Post Posted: Aug 28, 18 20:29

Thank you for the heads up greatly appreciated!  
 

Page 1 of 1