-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension injecting JS in browser #89
Comments
Unfortunately, i am not managing the extension anymore 😞. I transferred the extension to another group, and looks like they are doing some harmful things to the extension. Let me see if i can bring the original extension back. |
Oh, that's unfortunate. I'm not sure what all is involved with maintaining it but I would be willing to help out. |
One possible way is to upload the extension again with different name, but i don't know if this will violate Chrome app store policy |
Hello @nqbao are you the original developer of the extension? |
Yeah i am. |
I also am willing to help out, the chromesniffer extension is good and important for my work. I suggest rename the project by the previous name: AppSpector. I think that the extension not violate Chrome App Store policy because there are similars extensions. Even there are extensions of payment of the same type of chromesniffer. We are going to publish the extension again? Let's do it. |
I think we can not use the previous name I can also add you as collaborator if you want. |
I like "Framework Inspector" or Framespector or... WhatsFramework? What do you think? Other thing... I installed manually chromesniffer version 0.3.2 but Chrome updated to 0.3.6 and then disabled the extension with a message saying the extension violates the Chrome Store policies. Why this extension is updated? |
Can you try changing the name of the extension in the manifest? |
Let's go with Framework inspector. |
FYI: i started development on this repo https://github.com/nqbao/framework-inspector |
Excellent! I suggest that you remove the files the this repository and update the README with a link to new the project's repository I go to clone the "Framework Inspector" project. Cheers. |
Please add me as a collaborator. I love this extension and hate ppl that like to inject malicious scripts just to earn $.01 for a click. |
@nqbao, add me as a collaborator too. |
Added, please make sure you guys send a PR for your change 👍 |
I will close this issue for now. |
ok
…On Wed, Jan 4, 2017 at 12:01 AM, Bao Nguyen ***@***.***> wrote:
I will close this issue for now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#89 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEzIkpLk8QxtgRX0bsgqk3_aJXt_xoDGks5rOye5gaJpZM4KxrzY>
.
--
*S. Jenkins **Mailing Address: *
311 New Bern Avenue
Post Office Box 28933
Raleigh, North Carolina 27601-1417
*Cell: *919.926.8679
*Email*:
smjenkins1@gmail.com
*Skype: *
smjenkins95
<http://plus.google.com/u/0/+SeanJenkins>
|
I noticed the extension was updated and tried to inject this JS file, http://s3.eu-central-1.amazonaws.com/forton/cbp/cmps/50_c211e.js. When removing the extension you are taken to a fake news website.
The extension has also been removed from the webstore, https://chrome.google.com/webstore/detail/homgcnaoacgigpkkljjjekpignblkeae
Was the extension hijacked from the webstore?
The text was updated successfully, but these errors were encountered: