I went ahead and installed that app to see. It was in the service state when I did so. I killed it and enabled realtime on the CPU view. It was gone, but came back quickly. Its start time was reset though, so the kill function did stop it, but it just came right back.
The icon in the status bar is a pretty good indication of what they are likely doing. When you create a service in Android, you can request the be a service be started by "startForeground". This tells Android that your service is very important to the user, above others, and to do its best to keep you running(at the expense of requiring an icon to be always present in the task bar). When you killed it, it left free memory in the system, and the most important thing that could fill the gap was Vopium.
That would be my guess as to this behavior. More importantly, is it using large amounts of processor while it's backgrounded?
Robert