Your destination for complete Tech news

XSS on (Samy Kamkar)

5.71K 0
3 min read

In this blog post, we are going to discuss one of the interesting findings of Nirmal Dahal, Head of Security at CryptoGen Nepal Pvt. Ltd. on the website of Samy Kamkar ( Before jumping into the technical details, let’s discuss the target of the attack. Samy is an American privacy and security researcher, computer hacker, entrepreneur and a big influencer for many InfoSec members. Samy Kamkar is the person who created the first JavaScript-based worm known as Samy Worm which went viral within a few hours ultimately compelling myspace to shut down temporarily. 

Samy’s Twitter Handle

While he was explaining the work of Samy Kamkar to one of our co-workers, he happened to stumble upon Samy’s website. The site has so many Easter-eggs like challenges. Visitors of the site are not allowed to view the source code using normal methods like ‘right-click’, ‘Inspect element’, ‘Ctrl + shift + I’ etc. After trying the following snippet.


He was able to see the source code that was extracted from the DOM for the Samy’s website. 

You can go to and try to right-click, view his source code using CTRL + U or even go to another tab and type: 


Lastly, try to view the source using the inspect element and comment if you find anything interesting. Please reply if you find any other way to view the source code. 

After exploring through resources on the website, Mr. Dahal saw that he was using JS code to detect proxies like Burp, Charles & Fiddler. Finding it interesting, Mr. Dahal dug deeper to see everything Samy was using to make the website as interesting as it was. This search leads to a suspicious “jsonp endpoint” that was used to reflect the public IP address of whoever is requesting his website. 

Verifying proxy tools.
This code was verifying if the user was logged in or not. 
Vulnerable EndPoint  

The endpoint was something like then it would reflect something like this  

1st Image

Upon viewing the endpoint he started to alter the endpoint. Removing ‘st’ from the endpoint also removed it from the reflected output. 

2nd Image

Mr. Dahal continued to alter the endpoint and added ‘<>’ which was successfully reflected on the site.  

3rd Image

The output made him realize the endpoint was vulnerable to XSS and used one of his custom scripts to reflect a cross-site scripting vulnerability that was successfully executed. 

R-XSS DOM Overwrite  

Video PoC :

Timeline :

  • June 6, 2019 – Report Sent 
  • June 7, 2019 – Fixed & allowed to publish by Samy Kamkar 

Note: Finding an XSS issue in Samy Kamkar’s site, one of the first JavaScript-based worm creator, proves that no system can be 100% secure no matter how much experienced the owner/developer is. It is only a matter of time and the amount of knowledge to discover a new or even existing flaw.

Samy’s Mail 

धन्यवाद !!!

For More:

Leave A Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.