Signed in
We value your privacy
This site uses cookies to improve your browsing experience, analyze site traffic, and show personalized content.
Welcome to Pump.fun!
Pump lets anyone create coins, giving everyone equal access to buy and sell from the start. Prices can move quickly, so trade carefully.
By clicking this button, you agree to the Terms and Conditions, Privacy Policy, and certify that you are over 18 years old.
We value your privacy
This site uses cookies to improve your browsing experience, analyze site traffic, and show personalized content.
Paired with SOL| No holders yet. | ||||||||||
In September 2010, Twitter was hit by one of the strangest viral hacks in the platform’s history, later known as the “Rainbow Twitter Worm” or the “onMouseOver Worm.” The attack exploited a vulnerability in Twitter’s web interface using malicious JavaScript code hidden inside tweets. What made it terrifying at the time was that users did not even need to click anything. Simply moving the mouse cursor over an infected tweet could automatically activate the exploit. Once triggered, the worm would: force users to repost the malicious tweet automatically, spread itself across thousands of accounts within minutes, redirect users to random websites, create flashing colors, black screens, and visual glitches, and in some cases execute unexpected browser actions. The worm rapidly spread across Twitter and became a massive internet event. Many users thought Twitter had been completely hacked or that it was some kind of large-scale cyber experiment. Screenshots of rainbow-colored tweets, broken timelines, and infected accounts flooded social media. The exploit used JavaScript combined with the HTML “onmouseover” event, which allowed code execution when a user hovered their mouse over a tweet. At the time, Twitter had insufficient filtering protections against this type of script injection. Security researchers and hackers quickly began analyzing the code in real time, while Twitter temporarily disabled parts of the website to stop the spread. The platform eventually patched the vulnerability and removed the malicious tweets. The incident became one of the earliest viral social media worms and is still remembered as one of the most chaotic moments in early Twitter history.