Skip to main content

Timeline for Remove long string from files

Current License: CC BY-SA 3.0

12 events
when toggle format what by license comment
Oct 16, 2015 at 10:23 comment added h.j.k. Ah, found it on Security.SE.
Oct 14, 2015 at 7:30 comment added Giacomo1968 What everyone else says plus this advice. If you keep a clean backup or have your source code in a repository such as GitHub, you could quickly solve this infection by just destroying the infected code and deploying a clean code base. That said the infection came from somewhere. So even if you deploy new code it still doesn't mean that your server is safe. Meaning if this is PHP code you need to plug up the holes. If this is a WordPress site, you would need to upgrade WordPress to patch the holes. Plug-ins as well. Don't patch? It's just a matter of time before this happens again.
Oct 14, 2015 at 3:00 comment added h.j.k. You should at the same time ask about how to assess the current impact/damage on your environment, and future remediation over at Security.SE.
Oct 14, 2015 at 1:51 history tweeted twitter.com/StackUnix/status/654112321976070145
Oct 14, 2015 at 0:54 comment added andrewtweber Obfuscated aka somebody got into your server and maliciously inserted that code into your PHP files. You have a security loophole somewhere
Oct 13, 2015 at 22:36 comment added Ismael Miguel That isn't corrupted. That's "obfuscated" code! Burn your server and start over! DON'T. USE. IT. AGAIN. I hope I'm being just paranoid.
Oct 13, 2015 at 20:47 answer added glenn jackman timeline score: 5
Oct 13, 2015 at 20:38 answer added Gravy timeline score: 0
Oct 13, 2015 at 20:25 answer added Wildcard timeline score: 2
Oct 13, 2015 at 20:23 history edited jasonwryan CC BY-SA 3.0
Formattng and tag
Oct 13, 2015 at 20:22 review First posts
Oct 13, 2015 at 20:27
Oct 13, 2015 at 20:20 history asked user138341 CC BY-SA 3.0