Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

This question:

Can Someone Tell Me Why This Is malicious..?

someone has pasted code that (at a minimum) makes my ESET AV shut down my connection. Can someone with an appropriate sandbox edit that out?

share|improve this question

closed as off-topic by Martijn Pieters, Shadow Wizard, CRABOLO, nicael, rene Sep 29 '14 at 18:54

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This question pertains only to a specific site in the Stack Exchange Network. Questions on Meta Stack Exchange should pertain to our network or software that drives it as a whole, within the guidelines defined in the help center. You should ask this question on the meta site where your concern originated." – Martijn Pieters, Shadow Wizard, CRABOLO, nicael, rene
If this question can be reworded to fit the rules in the help center, please edit the question.

Do you mean... you actually ran that payload? – Frédéric Hamidi Nov 9 '12 at 18:12
No, just browsing to the page set off ESET. – Joe Nov 9 '12 at 18:17
Some antivirus software is particularly stupid when it comes to stuff like that; it doesn't realize that the code won't actually be executed, it just sees it coming in over the network and panics – Michael Mrozek Nov 9 '12 at 18:20
The angle brackets of the <script> tags are escaped, and the content resides in <pre><code>. Quite a paranoid tool indeed. – Frédéric Hamidi Nov 9 '12 at 18:21
Stupid NOD32. :( – Joe Nov 9 '12 at 18:26
@MichaelMrozek it's just trying to be there for you, man. What if you were running Opera? – Pops Nov 9 '12 at 19:15
@Pop, ah, sorry for my now defunct comment, those were indeed escaped <form> tags. Let's hope they at least handled escaped <script> tags in their unit tests. – Frédéric Hamidi Nov 9 '12 at 19:19