NAS Codex › QNAP › QNAP NAS with high CPU usage or a slow web interface: how QNAP says to find the cause
QNAP NAS with high CPU usage or a slow web interface: how QNAP says to find the cause
The QTS web interface is slow, or the NAS shows unusually high CPU usage. QNAP's FAQs give a short way to find the cause: use Resource Monitor to see which process is using the CPU and memory, disable the app behind it to confirm, and if neither CPU nor memory is high, check the browser. QNAP also warns about one specific high-CPU process, [oom_reaper], which a reported bitcoin miner imitates. This page covers all three.
Written against: QTS and QuTS hero (QNAP FAQs last modified 2022-03-30 and 2022-06-24). Last Updated: November 2026. Vendor menus and wording change between versions; if yours differ, follow the vendor page linked under Sources.
Before anything else: if the data on this NAS is not backed up somewhere else, copy it off first. Do not continue with any step on this page until you have.
Fast Answer
Log in as an administrator and open Control Panel > System > Resource Monitor. Click Processes, enable Group by Application, and sort by CPU or memory. Disable the top app in App Center to see whether the slowness stops. If CPU and memory are not high but the web interface is still slow, try an incognito window or clear the browser cache. If a process called [oom_reaper] takes around half the CPU, check its PID over SSH: QNAP says a PID above 1000 points to a bitcoin miner.
Step 1: find the process in Resource Monitor
QNAP's FAQ on a slow NAS says to use Resource Monitor to find which process causes the slowness in the web interface:
- Log in to the NAS as an administrator.
- Go to Control Panel > System > Resource Monitor.
- Click Processes, then enable Group by Application.
- Sort the processes by CPU usage or by memory, and find the process using the most of either. In QNAP's example, Ubuntu Linux Station uses the most CPU.
A second QNAP FAQ, for QTS 4.4.1 and later on all NAS series, describes the same place: Control Panel > System > Resource Monitor > Processes, where you can filter the processes by CPU usage or memory to see which ones are using the resources and manage the NAS's tasks better.
Step 2: confirm by disabling the app
QNAP's next step is to go to Control Panel > App Center and disable the apps you found in Step 1, to confirm whether they cause the slowness. If the web interface speeds up with the app disabled, you have found the cause.
Step 3: if CPU and memory are not high
QNAP says that if Resource Monitor does not show high CPU or memory usage but the web interface is still slow, open the web interface in your browser's incognito mode, or clear the browser cache, and check again.
The [oom_reaper] process: a reported bitcoin miner
QNAP has a security FAQ about one process in particular. It says a bitcoin miner has been reported to target QNAP NAS. On an infected NAS, CPU usage becomes unusually high, and a process named [oom_reaper] can take around 50% of the total CPU. QNAP says this process imitates a kernel process, but its PID is usually greater than 1000.
To check the PID, QNAP gives these steps:
- Access the NAS over SSH.
- Run
ps | grep oom_reaperand check the output. In QNAP's example the PID is 580.
- PID below 1000: QNAP says the process is a normal system process.
- PID above 1000: QNAP's instructions are to update QTS or QuTS hero to the latest version, install and update Malware Remover to the latest version, use stronger passwords for the administrator and other user accounts, update all installed applications to their latest versions, and not expose the NAS to the internet, or avoid using the default system port numbers 443 and 8080.
QNAP links this FAQ to its security advisory on the [oom_reaper] bitcoin miner.
Summary of QNAP's order
- Resource Monitor > Processes, grouped by application, sorted by CPU or memory.
- Disable the top app in App Center to confirm.
- No high CPU or memory but still slow: incognito mode or clear the browser cache.
- An
[oom_reaper]process near 50% CPU: check its PID; above 1000, follow QNAP's malware steps.
When to stop and get help
If the [oom_reaper] PID is above 1000, treat it as QNAP does, as a malware infection: update QTS or QuTS hero and Malware Remover, change to stronger passwords, update every app, and take the NAS off the internet or off the default ports 443 and 8080. If the drives also never spin down, see drives won't enter standby mode.
Questions
How do I find what is slowing down my QNAP NAS?
QNAP says to open Control Panel > System > Resource Monitor > Processes, enable Group by Application, and sort by CPU or memory. Then disable the top app in App Center to confirm whether it causes the slowness.
Why is the QNAP web interface slow when CPU usage is low?
QNAP says that if Resource Monitor does not show high CPU or memory usage but the web interface is still slow, you should use the browser's incognito mode or clear the browser cache and check again.
Is [oom_reaper] on my QNAP a virus?
QNAP says a reported bitcoin miner imitates the kernel process [oom_reaper] and can take around 50% of the CPU. Check its PID with ps | grep oom_reaper over SSH: below 1000 is a normal system process, above 1000 means following QNAP's malware steps.
Sources
Every fact on this page comes from the vendor documents below, opened on 2026-11-17.