Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

4/13/2009
01:32 PM
Connect Directly
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Twitter Visited By Worms Instead Of Bunnies

An exploit of a cross-site scripting flaw in Twitter sent almost 10,000 spam tweets and compromised at least 190 accounts over the weekend.

Over the weekend, a computer worm attacked the Twitter messaging service in three distinct attacks, generating almost 10,000 spam tweets -- as online posts are called in Twitter's twee terminology -- and compromising at least 190 accounts.

In a post on the Twitter blog, company co-founder Biz Stone said that no sensitive information was compromised as a result of the attacks.

The worm uses a cross-site scripting (XSS) flaw in Twitter to send spam tweets from infected accounts. The infection appears to have started when the worm's creator opened four new Twitter accounts containing the infectious code. The worm spread when Twitter users viewed the user profiles of the infected accounts.

"This is particularly nasty because you could get infected simply by viewing somebody’s profile page on Twitter that was already infected," explained developer Damon Cortesi in a blog post Saturday. "If you visited an infected profile, the JavaScript in the profile would execute and by doing so tweet the misleading link, and update your profile with the same malicious JavaScript thereby infecting anybody that then visits your profile on twitter.com."

The worm can be blocked by disabling JavaScript in your Web browser or by using the NoScript plug-in for Firefox.

The first attack struck about 2 a.m. PST on Saturday, and the Twitter security team worked to secure the service from about 7:30 a.m. PST through about 11 a.m. PST. Some 90 accounts were compromised.

The second attack struck later that afternoon. It affected about 100 accounts.

The third attack began Sunday and affected an undisclosed number of accounts.

Twitter's Stone said the company is still reviewing what happened, cleaning up, and watching for further incursions. "Every time we battle an attack, we evaluate our Web coding practices to learn how we can do better to prevent them in the future," he said. "We will conduct a full review of the weekend activities. Everything from how it happened, how we reacted, and preventative measures will be covered."

Previous
1 of 2
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Google's new See No Evil policy......
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31664
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 44741ff99f7a71df45420635b238b9c22093647a contains a buffer overflow which could allow attackers to obtain sensitive information.
CVE-2021-33185
PUBLISHED: 2021-06-18
SerenityOS contains a buffer overflow in the set_range test in TestBitmap which could allow attackers to obtain sensitive information.
CVE-2021-33186
PUBLISHED: 2021-06-18
SerenityOS in test-crypto.cpp contains a stack buffer overflow which could allow attackers to obtain sensitive information.
CVE-2021-31272
PUBLISHED: 2021-06-18
SerenityOS before commit 3844e8569689dd476064a0759d704bc64fb3ca2c contains a directory traversal vulnerability in tar/unzip that may lead to command execution or privilege escalation.
CVE-2021-31660
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 85da504d2dc30188b89f44c3276fc5a25b31251f contains a buffer overflow which could allow attackers to obtain sensitive information.