Give help. Get help.

  • # May 4, 2013 at 3:14 pm

    I have a problem Editing The footer on my WordPress MagPress Theme (Bizom)

    I’ve Tried Many things to get rid of this malicious code please Guys Help Me

    I don’t know If i missing something But here is my Code which is encrypted with base64

    < ?php
    add_action(‘admin_init’, ‘mytheme_add_init’);
    add_action(‘admin_menu’, ‘mytheme_add_admin’);

    # May 4, 2013 at 4:20 pm

    take that line and replace the word `eval` with `print`. That’ll show you the raw code they’re eval’ing.

    You say it is “malicious,” what is it doing? It looks like the author is simply trying to force you to have a link to his site in your footer. How is this theme licensed? Are you required to keep the links?

    My recommendation, in any case, would be to dump the theme and be very verbal in your criticism of the author. There is no legitimate reason to obfuscate code like this. Even if this particular code is not malicious, it is Not A Good Thing.

    # May 4, 2013 at 4:56 pm

    function theme_usage_message() { global $themename, $shortname; $rk_url = get_bloginfo(‘template_directory’); echo (“
    “); echo (“
    “); echo (“
    Opps..You Have Modified The Footer Links..This Theme Is Now Deactivated!
    “); echo (“
    This Theme Is Released Free For Use Under Creative Commons Licence. All Links In The Footer Must Remain Intact AS IS. Please Appreciate These Supporters Effort In Providing You This Great Theme For Free.
    “); echo (“
    Please Follow These Steps To Restore The Footer:

    Please redownload $themename Theme directly on our website.
    Delete, upload and activate the theme again.
    Finally, refresh your page to go back to your homepage.

    “);} function check_theme_footer() { $l = ‘Bizom WordPress Theme By’; $f = dirname(__file__) . “/footer.php”; $fd = fopen($f, “r”); $c = fread($fd, filesize($f)); fclose($fd); if (strpos($c, $l) == 0) { theme_usage_message(); die; }} function check_theme_header() { if (!(function_exists(“functions_file_exists”) && function_exists(“theme_footer_v”))) { theme_usage_message(); die; }} function functions_file_exists() { if (!file_exists(dirname(__file__) . “/functions.php”) || !function_exists(“theme_usage_message”) ) { theme_usage_message(); die; }} add_action(‘wp_head’, ‘check_theme_header’); add_action(‘wp_head’, ‘functions_file_exists’); check_theme_footer();

    that’s it traq thank you for your time and by the way i don’t have money to buy the theme please if you could help do it i count on this website revenue … i don’t even have a payed domain name or hosting

    # May 4, 2013 at 6:08 pm

    Odd way to obfuscate code like that… every one and their mother can decode base64.

    Why is leaving the attribution in the footer not an option?

    # May 4, 2013 at 9:13 pm

    > i don’t have money to buy the theme

    That’s besides the point. Regardless of how you or I feel about sneaky-looking code, if you don’t intend to abide by the terms of this theme’s licence, then you **should not use it**. Just because I don’t agree with obfuscating code and man-handling clients into obeying license terms doesn’t mean that I think it’s *remotely* acceptable to try and circumvent them.

    In showing you how to see this code (I’d already decoded it, I knew what it did), I wanted you to be able to confirm that – however “crappy” – there was no “malicious” code hidden inside. I **do not approve** of ignoring copyrights and violating licenses, and I will not assist anyone in doing so.

    It looks like the author of the theme is releasing his code under a CC-BY license. That makes it free and open-source, so long as you include attribution to the original author (i.e., the links in the footer). The Creative Commons licenses **are** legally binding and you could be setting yourself up for trouble, especially since you are going to such efforts to break the license terms.

    > i count on this website revenue

    that doesn’t help your argument. Quite the opposite.

    # May 4, 2013 at 9:48 pm

    I would vote to close this discussion as the user is clearly trying to find a loophole in breaking the EULA.

Viewing 6 posts - 1 through 6 (of 6 total)

The topic ‘Encrypted code base64 Problem [Closed]’ is closed to new replies.