No Image

Twitter is strange when it comes to business accounts

I created my company’s Twitter account, called  @EndpointCS . Obviously, I tried to add the birth date of the company: 1.1.2015. Well, imagine what happened next with my brand new account: it got locked because the owner of the account must be at least 13 years old. And my company is only 6 years old. I had to submit a photo of my ID in order to get it unlocked. Fortunately, and very surprisingly for me, the process took a few minutes. Did they automatize it ? I think so… otherwise it couldn’t have been so fast.   So, Twitter, get your processes straight. In  case you’re wondering, there is no official way to set up a business account. You still need a person to create it and mark it as such. And that person must be 13 years or older. 🙂  

My IT_SecurityNews account nominated for “Best tweeter” account in the European Cybersecurity Blogger Awards

European Cybersecurity Blogger Awards – VOTE FOR YOUR WINNERS: Vote here . Yes, it is a Google Form… but there is no malware or spam 🙂 Don’t forget to vote IT_SecurityNews! The seventh annual European Cybersecurity Blogger Awards sponsored by Qualys and powered by Eskenzi PR, will be bestowed upon the best cybersecurity bloggers, podcasters, Tweeters, Instagrammers and vloggers in a live virtual event on Tuesday 2nd June 2020. Visit IT Security news and the Twitter account.

Logginggate: Twitter has been logging your password in plain text all this time… and this is not all of it!

Did you receive this email too ? Twitter is telling us that despite the fact that they stored the just the hashes of the passwords in their DB, they have been logging the plain text password in their backend. Stupid ?! Hell yes! But the even more stupid thing is this: WHY DO THEY SEND THE PASSWORD IN PLAIN TEXT TO THEIR BACKEND ? It would be enough the generate on the client side the password’s hash and send only the hash to their server. Now it all makes sense… In the past weeks they have been blocking accounts under the excuse that the user violated their usage rules. This is bullshit… I think they were just trying to piss people off so that they change their password.     And here is the relevant part in plain text:   About The Bug We mask passwords through a process called hashing using a function known as bcrypt, which replaces the actual password with a random set of numbers and letters that are stored in Twitter’s system. This allows our systems to validate your account credentials without revealing your password. This is an industry standard. Due to a bug, passwords were…

Quoted on over the 32,8 M Twitter accounts leaked

Source: Author: Ionut Arghire, Security Week   The cybercriminal behind the claimed Twitter leak is the same hacker who was previously attempting to sell stolen data from Myspace, Tumblr and VK user accounts, namely The Twitter credentials have already made it online on paid search engine for hacked data LeakedSource, which says it received a total of 32,888,300 records, each containing user’s email address, username, possibly a second email, and a password. [..] What is yet unclear is how old the supposedly leaked data is, since LeakedSource doesn’t provide specific details on that, although they do suggest that some credentials might be only a couple of years old. Furthermore, IT Security expertSorin Mustaca tells SecurityWeek that the manner in which these credentials were stolen isn’t that clear either. “Interesting enough, Leakedsource writes that they “very strong evidence that Twitter was not hacked”, rather the users got infected with some malware which stole credentials directly from the browsers of any account, not only Twitter’s,” Mustaca says. “However, there is no clear evidence presented that this is indeed the case. Their explanation for malware stealing credentials from browser is not entirely valid.” Although malware that targets browsers to steal user…

No Image

onMouseOver() Twitter security flaw (+Update)

A Twitter security flaw is being widely exploited on Twitter, showing remote content from third-party websites without user’s consent. The flaw uses a JavaScript function called onMouseOver() which creates an event when the mouse is passed over a text or link. Any user can use this flaw to create simple popups, redirect the page to somewhere else, retweet some messages or hide parts of the message. The link has to be constructed in such a way that it starts with<text>@”onmouseover=”<code>” The problem is that Twitter doesn’t filter the code, it instead executes it. To overcome the problem, use some 3rd party websites to work with Twitter. These website use the API directly and not the website GUI. Another solution is to use the mobile website, which doesn’t seem to have the flaw. Update: Twitter fixed the problem :

No Image

When the whales fly (or Twitter hiccups)

From time to time, the users of Twitter are unable to login on the official website. Sometimes the screen below can be seen, sometimes just a timeout error. Interesting enough, after you refresh a couple of times, you are able to do whatever you were trying to do, and then never get this error until you login again. There can be many reasons for which we see this error. From a simple overload to a distributed denial of service. Which we know that it happened on August 6, 2009 [1]. But, the most common reason is too many users(or services) are trying to access the Twitter services simultaneously. In this case, the servers behind the domain are overloaded and are not able to access the required information to let you in. There is a corresponding HTTP error which is reported : 503 – Service (or server) not available. But what is this error and why are we able to see it when the webservers are not available? There’s a trick. Any decent webserver reserves a certain amount of connections for this kind of messages. This error code can be served in the following circumstances: – Too many connections simultaneously….

No Image

Facebook and Twitter Phishing (on first sight)

The source of the articles is in the Avira Techblog: Twitter Phishing (on first sight) Facebook Phishing (on first sight) Twitter Over the weekend our spam traps received a massive wave of emails looking like the one below: The emails seem to stem from “Twitter Support” ( and are addressed each to exactly one unique email address. The link in the email seems to be unique for each email sent, too. Quite an effort to make the email look more legitimate. The target link is always a compromised website holding an html page. Amazon: Bestsellers Electronics and Photo After clicking on the URL, a multiple stage redirection takes place. On some of these redirection websites, the intermediate page raises alerts because our engine detects encrypted content in JS. Finally comes the surprise: The target website at the end of the redirects is not a phishing website but a Canadian online pharmacy. For me personally this was a “Wow!” moment. Why did the spammers choose to send the emails as Twitter phishing? I think that the explanation is simple – they did it because nobody did it before. As usual, users of the Avira Premium Security Suite and the users of…

No Image

Are your tweets through Tweeterfeed and no longer published ?

Are you using Tweeterfeed and ? Are your tweets no longer published ? Then you didn’t read Twitter’s post here: June 30, 2010 The @twitterapi team will be shutting off basic authentication on the Twitter API. All applications, by this date, need to switch to using OAuth. Read more » So, the solution is to switch to OAuth. is now able to use this : Guys at Tweeterfeed and : are you stupid ?! You f** up a lot of messages and you made a lot of people in this world ! Shame on you.

%d bloggers like this: