High CPU and High Bandwidth caused by unknown Process


  • This is unfortunately the second time this has happend to me and I am cluelesss on why this has happened.

  • I have a droplet which is running at 100% CPU and is consuming loads of Bandwidth, so my billing is going through the roof… I can see from the digital ocean Graphs that its caused by some strange process with some letters e.g. bctouovovf.

  • I have restarted the Droplet

  • Have run Clamv, rkhunter

  • Habe ufw enabled and still…

Is there someone who can help to find out what this is?

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hey friend!

At the “top” screen press C and watch that name change. I’ll bet the filename of the process looks like someone just smashed their keyboard to name it. I would submit the probability that your server has been compromised, and that this task is masking it’s true nature. The C button will unmask it a bit, typically.

It’s running as root too, so you can’t really save this machine and know you’re safe. You should prepare your backups to create a new droplet, and use this one to investigate how it was compromised. If you find the filename of the running application, you can use the “stat” command to grab some vitals, like this:

stat /path/to/file

The time/date in which it was created will often correlate to a log entry for a running service on the system, allowing you to track it’s origin. I know that’s a bit vague, but that’s because there is no one path to this, it’s very dynamic.


i guess you can install htop (like task manager) and check what proccess is using resources and kill it. if you are on debian/ubuntu command is

apt install htop