Protecting yourself from malicious *JS scripts
Root / Submissions / [.]
MasterR3C0RDCreated:
So you've been looking to make your experience on the site a bit more interesting. You find a script, and run it without looking at it. At this point, you've already practically given your account to whoever wrote it. Common sense and rational thinking can help you a lot when deciding which scripts to use and which scripts not to use. Here, I'll highlight some ways to tell what a script is doing and what it isn't doing
Replying to:ElzoBro
Can't an Admin just make it impossible to reference cookies in the JS? Maybe just block the word Cookies or somethings like that.
Sorry, not how it works. It can't be blocked without breaking scripts
Replying to:Minxrod
Maybe you could add something about using the "find word' function some browsers have to automagically check for document.cookie. Scanning it manually might miss it. Obfuscation is more obvious, so no automatics there.
It can be pretty simple to find document.cookie in a script, even for people with no knowledge of JS. Basically, just be skeptical if the script doesn't look right.
Replying to:Minxrod
Maybe you could add something about using the "find word' function some browsers have to automagically check for document.cookie. Scanning it manually might miss it. Obfuscation is more obvious, so no automatics there.
Ok.
Replying to:haloopdy
It's not just cookies they can take. They can simply look at your password when you login by pulling the text right out of the input field. They just have to add an event to the login submission that takes the password and sends it off to their server.
You have to be logged in for personal JS to run question mark.
Replying to:haloopdy
It's not just cookies they can take. They can simply look at your password when you login by pulling the text right out of the input field. They just have to add an event to the login submission that takes the password and sends it off to their server.
All they have to do is fake the login area and make it look like you're not logged in (even though you are). It's not too hard to do.
Replying to:haloopdy
It's not just cookies they can take. They can simply look at your password when you login by pulling the text right out of the input field. They just have to add an event to the login submission that takes the password and sends it off to their server.
More code == More noticeable.
Replying to:haloopdy
It's not just cookies they can take. They can simply look at your password when you login by pulling the text right out of the input field. They just have to add an event to the login submission that takes the password and sends it off to their server.
Sure, it would be a more complex attack vector. But it could easily be hidden on another server, and the JS they install could simply load this other code, so you really need to be careful.
Oh, and BTW, If it loads another JS script from another server, don't use it.
Replying to:RGamesOffical
Oh, and BTW, If it loads another JS script from another server, don't use it.
This can be argued. If you're using a script that requires a well-known and respected library (and jQuery), it is probably safe. As always, just be careful about what you look at.
Replying to:RGamesOffical
Oh, and BTW, If it loads another JS script from another server, don't use it.
Like, the LZ loader is 100% safe as long as long as you donโt load any bad scripts from LZโs Repository.