Editing triggers popup asking for username and password – security breach?

  • Hello,

    I’m using a WordPress 2.7.1 version and I’ve been holding back from upgrading because of some pending issues with Unicode (for those of you familiar with WordPress’s Unicode issue: this blog was started back in the days of WP Ver 1.6 or so, the MySQL charset and pagination issues are quite complex) and I came across the below problem yesterday:

    Whenever I open up an existing post and hit the “update post” button, a window pops up with the below details:

    Title: Authentication Required
    Text: The server (our server domain, e.g. DOMAIN.COM) at Magic requires a username and password.
    Entires: User Name: ____________________ Password: ____________
    Buttons: Log In, Cancel
    Screenshot: https://www.flickr.com/photos/yonghokim/3772683834/

    I attempted entering dummy ID and password and the pop up will go away for 0.5 sec and then come back again. I suspect this is some form of trojan so I didn’t enter our real password.

    When I press cancel, I am sent to /blog/wp-admin/post.php with a blank screen with a “Access Denied” message (Screenshot: https://www.flickr.com/photos/yonghokim/3772683860/ )

    This popup is triggered when I hit the “update post” or “update page” button. The fact of whether contents of the textarea actually changed or not doesn’t matter – clicking the “update page” triggers the popup. It doesn’t happen when I post a new post. I haven’t seen the popup in other areas of the backend or frontend.

    My symptom is similar to https://www.ads-software.com/support/topic/247792 except I can seemingly do all tasks – logging in, posting, etc – except editing.

    More information about this WordPress install:

    I use the below plugins:
    Akismet 2.2.6
    Attachment Manager 2.0.2
    Audio player 1.2.3
    Breadcrumb 0.5.1
    Breadcrumb Navigation XT 1.7
    CountPosts 2
    Disable Revisions and Autosave
    Flickr Photo Album 1.1
    One Click Plugin Updater 2.4.13
    Search Pages 2.3
    TanTanNoodles Simple Spam Filter 0.6.2
    WordPress.com Stats 1.5
    Wordpress Automatic Upgrade 1.2.5
    WordPress Database Backup 2.2.2

    I did a major cleanup of plugins that kept obstructing the admin area with their upgrade notices, even when they were inactive plugins. I deleted a bunch of folders that belonged with the plugins; one of them was the XDRS(sp?) OpenID service framework.

    I run this WordPress install on a VPS, and there are a couple other domains running WordPress and MediaWiki hosted along. One of the other WordPress installations was hacked on October of 2008, (the hacker deleted a month worth of postings and left a notice saying “This website was hacked by Daazle(sp?)” but I changed the admin password and haven’t noticed any strange behavior since then.

    I am hiding the URLs out of concern that this symptom may be the result of a scripted attack, and by giving out the affected website I may be notifying that the attack was successful, inviting for further exploits on the server.

    Any thoughts on why this could be or how to fix? I’m considering upgrading to WP 2.8.2 to see if this will overwrite my install of any compromised PHP files.

Viewing 15 replies - 31 through 45 (of 82 total)

  • I thought I had the “Authentication” problem solved by upgrading to version 2.8.2. After submitting a new blog entry and cleaning up the plugin problems, my blog just vanished. I am not able to access the site through the web or by trying to gain access through three different ftp programs. Did anyone else have this problem? I hope the hacker did not gain access to my username and password, and then change it.

    I had many plugin files that were also suffering from this problem. Perhaps they are not causing problems right now, but I’ll bet they can be activated.

    To find your infected files, if you have shell access, you can run this command:
    grep -r -l gzinflate .

    This will give you the list of infected files, and ones that legitimately have “gzinflate” in them. The bad ones are easy to spot, they have that some text tacked on to the top.

    Here is my list of infected files:
    [daxter]$ grep -r -l gzinflate .
    ./audio/2007/05/pbpost15.mp3
    ./wp-admin/includes/class-pclzip.php
    ./wp-content/plugins/akismet/akismet.php
    ./wp-content/plugins/organizer/plugin_hook.php
    ./wp-content/plugins/podpress/getid3/module.archive.gzip.php
    ./wp-content/plugins/podpress/podpress.php
    ./wp-content/plugins/preach/preach.php
    ./wp-content/plugins/runPHP/runPHP.php
    ./wp-content/plugins/simple-tags/simple-tags.php
    ./wp-content/plugins/tagthis/pclzip.lib.php
    ./wp-content/plugins/tagthis/tagthis.php
    ./wp-content/plugins/future-post.php
    ./wp-includes/class-simplepie.php
    ./wp-includes/http.php

    Interestingly, this is the list of my active plugins, less WP Super Cache. WP Super Cache might have been infected, but I updated when I was trying to fix the problem.

    Since it was the active plugins and not the inactive ones, the hack did not reach the plugin files directly through the file system. It must have some connection to the database or attached when the plugins were accessed.

    Yokima,

    I followed the process you described above, retrieving the 2.6 version of vars.php and saving it over the hacked file.

    Then I tried save a Test file and got this:

    Warning: Cannot modify header information – headers already sent by (output started at /home/blindfla/public_html/wp-includes/vars.php:73) in /home/blindfla/public_html/wp-includes/pluggable.php on line 770

    I used the back button to return to the Edit Post page, then went to Manage Posts, and found that the post was saved despite the warning. I then tried editing and publishing a draft post following the same process. I got the warning again, but the post published.

    So I seem to be halfway there. I’m not getting the obnoxious pop-up anymore. What action do you suggest about the warning?

    Thanks so much for your trouble-shooting due diligence, Yokima. You rock!

    Thread Starter yokima

    (@yokima)

    williscreative: did you use vi or some other editor to edit vars.php? Then there may be blank lines or spaces before or after <?php and ?>.

    If you uploaded them via FTP, check the permissions – on my server they are set to 644

    scottop: Thanks. I found the below to be affected using grep:

    ./wp-content/plugins/tantan-reports/tantan_reports.php
    ./wp-content/plugins/tantan-flickr/flickr.php
    ./wp-content/plugins/breadcrumb.php
    ./wp-content/plugins/stats/stats.php
    ./wp-content/plugins/tantan-spam/plugin.php
    ./wp-content/plugins/search_pages.php
    ./wp-content/plugins/wp-db-backup/wp-db-backup.php
    ./wp-content/plugins/breadcrumb-navigation-xt/breadcrumb-navigation-xt.php
    ./wp-content/plugins/prevent-browse-happy.php
    ./wp-content/plugins/one-click-plugin-updater/oneclick-plugin-updater.php
    ./wp-content/plugins/akismet/akismet.php
    ./wp-content/plugins/audio-player.php
    ./wp-content/plugins/attachment-manager/wp-attachment-manager.php
    ./wp-content/plugins/wordpress-automatic-upgrade/wordpress-automatic-upgrade.php
    ./wp-content/plugins/countposts-v-10-wordpress-plugin/CountPosts.php

    The below seem to have gzinflate as part of their regular code (but check just in case)

    ./wp-content/plugins/one-click-plugin-updater/pclzip.lib.php
    ./wp-content/plugins/wordpress-automatic-upgrade/lib/pclzip.lib.php
    ./wp-includes/js/tinymce/plugins/spellchecker/classes/HttpClient.class.php
    ./wp-admin/includes/class-pclzip.php

    “Magic” attack solved by replacing the vars.php file thanks to yokima and tstalcup. I had 2.8.2 installed, and I replaced the vars.php file with the 2.7 version. And obviously for anyone else who has this problem do not enter your username and password into the authentication popup window.

    You really should replace your vars.php with one from the version that you are running. Replacing it with a different version could cause unpredictable errors.

    Can anyone describe this corrupted code in the plugins and where to find it? (I’m not a coder and don’t know where to look to see if I need to upload new plugins). Thanks.

    its at the top. you cannot miss it.

    Thread Starter yokima

    (@yokima)

    danceadvantage: here, have a screenshot: https://www.flickr.com/photos/yonghokim/3777646797/sizes/o/

    Running WordPress 2.3.3, replacing the vars.php from a local backup worked for me.

    Anybody have an Idea how this happens?

    Thanks for figuring this out.

    whooami cleaned my site and removed the hacked code!! THANK YOU!! Highly recommend!!

    If you are running an insecure older version and you simply replace files, be prepared for this to happen again. To help yourselves you should upgrade after you know your site is clean.

    I have had the same problem. I went into Pluggin editor and removed the code at the beginning of all of the pluggins.

    2 pluggins would not let me do it, so I deleted the pluggin. Those pluggins were “Super Cache” and “Google Site Maps”.

    I have deleted the cache, but it is still popping up. My site might need a little time to process the change I have made, but for now I am still waiting.

    there was MORE than code inside /wp-includes/var.php and some plugin files on stefarama’s site.

    I suggest that those of you that are looking at specific files in order to do a quick a simple ‘fix’, look at EVERYTHING.

    like was already said — if you dpnt do it right, it doesnt go away.

    I went back and took it off the vars.php file and I am ok now. Any pluggin that refused the update was deleted. Thank you all so much for the help.

    If it comes back, I’ll let you all know.

Viewing 15 replies - 31 through 45 (of 82 total)
  • The topic ‘Editing triggers popup asking for username and password – security breach?’ is closed to new replies.