![]() |
|
[Guide] How To Make Sure Your Chrome Extensions Are Secure - Printable Version +- Hack Forums (https://hackforums.net) +-- Forum: Tech (https://hackforums.net/forumdisplay.php?fid=444) +--- Forum: Computing (https://hackforums.net/forumdisplay.php?fid=88) +---- Forum: Computing Lounge (https://hackforums.net/forumdisplay.php?fid=8) +---- Thread: [Guide] How To Make Sure Your Chrome Extensions Are Secure (/showthread.php?tid=4945092) |
[Guide] How To Make Sure Your Chrome Extensions Are Secure - King of Hearts - Aug 11, 2015 Hello, A couple of days ago, I decided to code a Google Chrome extension for HF Live. Having never coded an extension before, I was a bit surprised with how easy it is to get one up in the Chrome store. To upload an extension to the Chrome store, all you need is a gmail account and $5. The reason I'm telling you this is to illustrate the ease of which one can upload an illegitimate product on the app store. One can easily upload an extension that listens to all the traffic and commit "affiliate fraud, credential theft, advertising fraud and social network abuse." Extensions make it extremely easy to inject javascript into pages and one can easily add code that listens to the sign in button on the yahoo mail page and upon clicking that button, the user is logged in to their yahoo mail but unknown to him, his info is also sent to the hacker's server. Today, I will be showing you how to easily check if the extensions you are using are backdoored. Before I do, I would like to explain a little bit about how chrome extensions work. Chrome extensions have three places where javascript that can be injected.
Now that you know exactly how and where code can be executed, there's one important thing you should know: the content script can easily communicate with the background script and vice versa. You will see why this is important in a second. How do you actually check if you're extension is running a backdoor? Well, first of all, you need to check what you are installing. Be cautious of extensions that "read (and/or change) all your data on the website you visit. These extensions can easily listen for post requests (for example when you login to a forum or purchase an item from ebay) and they can intercept the data being sent and along with sending it to the original requetor (e.g hackforums or ebay), they can also send it to themselves.
As you can see, if an extension is listening to your requests, the request has to go from your computer to the hacker's server. If you see a request to a suspicious website or if you see something being sent that you don't think should be sent, then you should uninstall the application right away. Also, one last note, if I were a malicious coder and I knew that my requests could be sent, I wouldn't be sending the requests right away. Rather, I'd wait a random amount of time or better yet, wait until the user closes the browser and then send the login/stolen information then. The best way around this is to take a look at the source code of the extension. You can take a look at where Chrome stores extensions here -KoH * - King of Hearts - Aug 29, 2015 Reserved for future use. -KoH * - Fish - Aug 29, 2015 nice post! im gonna see if my extensions are good. thanks for sharing * - Hamware - Aug 31, 2015 Awesome post mate, revamping the browser section. <3 * - bonjours_bonjours2015 - Aug 31, 2015 thank you bro for your post thank * - King of Hearts - Sep 7, 2015 (Aug 31, 2015 11:27 PM)xadamxk Wrote: Wow, this thread needs far more attention than it is getting. Thanks a lot. Hopefully, this will receive some hits from the next news edition. * - thefunstash - Sep 7, 2015 Thanks man. Well writ, solid advice. * - King of Hearts - Sep 29, 2015 (Sep 7, 2015 06:21 PM)thefunstash Wrote: Thanks man. Well writ, solid advice. Thanks. I'm glad you've found this useful. |