Let's break it down:
/bin/sh ps aux starts a shell and invokes the ps command with the "aux" switches (i.e., display all processes); that's a bit odd to me since you (or I would, anyway) use /bin/sh -c "ps aux" to accomplish what I think that implies; I get an error when I try to run such a command in a Cygwin bash shell; one other thing, the shell on an Android device is located in /system/bin and not in /bin/sh (unless you're in custom recovery, etc.)
that command's output get's piped to the next command:
grep -i dd searches the output of the prior command for the case-insensitive string "dd" (which is a disk utility)
next, that output is piped to:
grep -v ftp which says to search and discard any lines with "ftp" in them
But here's where it get a bit odd and breaks down, in my opinion since the next character after the above command is not the "|" (pipe) but is the ">" output redirection that will send the output to a file named in the next character string--"pkill" in this case; however, that "pkill" string appears that it should be a command all unto itself along with the rest of the characters in the command.
So, it kind of breaks down (again) for me there and just the whole thing smacks of someone mish-mashing some Linux commands together.