wordpress exploit, site hacked [newportalse.com]

Ciotti – You don’t lose anything if you delete FILES (except for if you delete your wp-content/uploads, wp-config and .htaccess). Everything else is on the database, safe as houses.

As for why a scanner misses stuff, well it’s not possible to know everything. This is what we call a backdoor injection, and if you’re not fully cleaning up everything on your site after you’ve been hit, and changing passwords, you will be reinfected, over and over, ad nasuseum, until you do.

I’m going to say this again, kids.

1) Backup EVERYTHING, database, files and all to your desktop/laptop whatever.
2) Delete ALL the file off your server except for wp-content/uploads,
3) Scan those files with your own eyes and if you see ANYTHING with .php, kill it with fire.
4) Get FRESH copies of WordPress, your themes, and plugins and upload them
5) Change ALL your passwords, from SSH and email to SQL and WordPress
6) Inform your host that this happened, so if they’re running insecure servers, they can take steps.

For what it’s worth, this means you’ll need to start over with a fresh .htaccess and wp-config.php file, but it’s better to add things back in one at a time when you KNOW they’re right than to risk this if you don’t know exactly how all this works.

Yes, it’s a pain in the ass, but this is a risk with any webapp on any server. It’s like getting ants in your house, or termites. Or fleas. Extreme measures.

@ipstenu

So, following your instructions, the sites would not lose any backlinks to them as along as wp-content/uploads etc. does not get deleted?

Sorry for all the questions, but I guess it’s how we newbies learn.

I’ve already changed all passwords to everything, should the next step be to log in to my FTP client and delete everything that you’ve stated minus wp-content/uploads?

It’s fine ?? This is how you learn.

The backlinks, posts, links, etc are all stored in your DATABASE, not in any files ?? That’s why it’s pretty much always okay to do this (sometimes, yes, it’s not, but that’s not today and any loss that comes with this is, I imagine you’ll agree with me here, FAR less than dealing with the effect of the hack).

There are only 2 files and one folder that store site data:

wp-content/uploads– Stores ALL uploaded media files (should be ONLY files named .jpg, .png, .mp4, etc etc – If you have ANY named .php or with .php in their name, you should delete them)

wp-config.php – This is your config file and has your database information. While I am telling you to delete it, you can very easily rebuild it without data loss (just put in the correct userid/password/database name). You can make a copy of the wp-config.sample file included in all WP downloads and use that as a basis to rebuild.

.htaccess – Unless you’re using a cache plugin or have a site that’s been around a long time, you probably only have the default one. When you go to re-save permalinks, you can easily recreate that, so it’s not going to hurt anything to rebuild it either ??

same problem with me https://www.speedrider.org
but its referring to internet-safeness.ru.

Same hack, speedrider, same directions as above. Scrub it all with fire.

https://www.speedrider.org

1. Have checked the .htaccess
2. Removed the explicit code wp-include/js/at |10n.js

But my site still referring to the malicious site.
Checked with https://sitecheck.sucuri.net/scanner/ and it says my site is clear…

sighhhhhhhh…….. it still not solved.
Going into WP dashboard, clicking any links in the dashboard will refer to the referral site.

Ive done every solution that you can find here, except for re-installing, and I can say they do not work, Sucuri doesnt find anything, and I’ve noticed a pattern that everytime I log into the wp-admin it redirects me…

jeaniusog, speedrider: The sitecheck (from sucuri) won’t be able to scan inside your wp-admin (after you login), since it doesn’t have your credentials to there. It is a free scanner that will only check the external pages.

It seems that you might have additional malware on other javascript files that are only included inside the admin interface, so try checking that or doing a clean update of WordPress overwriting all the core files.

*you could use firefox with noscript to bypass the redirection too and force an update from wp-admin.
**Also try clearing your browser cache. Sometimes the .js files get cached longer…

thanks,

It seems that you might have additional malware on other javascript files that are only included inside the admin interface, so try checking that or doing a clean update of WordPress overwriting all the core files.

No.

DELETE wp-admin

The whole folder. Just delete it. NOTHING in there is dangerous to delete. Once it’s gone, download a FRESH copy from www.ads-software.com/download and copy the folder up.

Really you should delete everything except wp-content/uploads (and backup your wp-config.php and .htaccess)

Then copy it all up from FRESH copies of the downloads. For ALL of your themes and plugins. Add in your personalized settings for wp-config.

@jeaniusog (and others) – follow Ipstenu’s advice. As [email protected] suggested, this particular injection attack does also affect files on the admin side. You are best off getting as clean an install as you can. Don’t just look for what you *think* might be infected. Get it all now and save yourself tears and headaches later ??

Just wanted to get this out there as well – same attack, also now redirecting to ijo7ruta.in (in case someone is searching this string).

Hello everyone, and thanks for the earlier email Chad, VERY appreciated. I am not live yet as I’m still still tweaking my site, but I did do a scan at sucuri.net and it said that I was clean. In reading all of the above I see that that is not necessarily the case tho. I don’t know if I did it correctly, but I opened my .htaccess, if I even ‘had’ the right one, with notepad and it said “empty”. In searching for l10n.js I found one located at wp-includes/js/l10n.js. I have no idea if I am indeed clean, or safe from future infection.

Update: I’m sorry, the .htaccess said…

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Hi all, I had the same newportalse problem, and I’ve deleted everything from my website https://www.blazingtruth.com and reinstalled a fresh copy of www.ads-software.com

I think I still have my content — that is, I can see all my old plugins and database files, but they are not appearing on the actual website. How would I go about fixing this? It seems like it would be a simple fix, yet with my lack of programming experience, this is all foreign to me.

Thank you all!
D

Just a note for everyone: This newportalse.com hack was definitely a hack that coincided with the timthumb.php vulnerability, which was discovered in early August.

I had updated that plugin/cleaned out the malware from the files that was recommended, but the newportalse.com flag in Chrome was still happening.

For those of you who came to this problem via the newportalse.com hack, you also need to go back and check for several other files in your WordPress installation.

Excellent details of how to do that are found here: https://techspheria.com/2011/08/phpremoteview-hack-what-it-is-and-how-to-remove-it/

I’d be interested if anyone continues to get flags for this hack after dealing with the Javascript file mentioned. Good luck folks.

Yep, just saw these files compromised:

jquery.js and variants like jquery-1.3.2.js
upd.php (new file)
wp-config.php (with permissions changed)

The JS files have code at the end that starts with “var _0x4de4”.
They can appear in various places in wp-content/themes, as well as in wp-includes.

The php files have a bunch or curl ops, like “curl_setopt”. In wp-config its hidden under a lot of white space.

Note, the new versions of timthumb.php fill up its cache with .txt files now, and they start off ominously:
<?php die(‘Execution denied!’);
But that is by design.

The web hosting company cleaned up some of it but those files were left over. They updated all the timthumb.php, it seems.

So far file dates are reliable.