---
title: Hunt: GL.iNet's infection check for the cloud-management compromise is a running process 'crond -i /tmp/.log' on routers and KVMs | ctxsec
url: https://ctxsec.com/items/hunt-gl-inet-router-kvm-infection-check-crond-i-tmp-log-process-luci-ssh-kvm-terminal
description: "GL.iNet published one indicator: the exact text crond -i /tmp/.log in a running process's details. If it's there, treat the device as infected; if the check finds nothing and there's no other reason for suspicion, GL.iNet says no reset or cleanup is needed."
status: "official (GL.iNet security notice, updated Nov 21, 2026)"
published: 2026-11-21
---

> GL.iNet published one indicator: the exact text crond -i /tmp/.log in a running process's details. If it's there, treat the device as infected; if the check finds nothing and there's no other reason for suspicion, GL.iNet says no reset or cleanup is needed.

[← Threat Hunting](/hunting) · [markdown](/items/hunt-gl-inet-router-kvm-infection-check-crond-i-tmp-log-process-luci-ssh-kvm-terminal.md)

official (GL.iNet security notice, updated Nov 21, 2026)

2026-11-21 11:44 AM ET

### Hunt: GL.iNet's infection check for the cloud-management compromise is a running process 'crond -i /tmp/.log' on routers and KVMs

- **Router, LuCI:** System → Advanced Settings → LuCI → Status → Processes, search for `tmp/.log`. **Router, SSH:** `ps | grep tmp`.
- **KVM:** Toolbox → Terminal → Access, then `ps -aux | grep tmp` (`ps -a | grep tmp` on the RMQ1). Run it on the KVM, not on the attached computer.
- A line showing only the grep command isn't a match.
- **If infected:** factory reset, or on KVMs install the security beta; then the stable fix when it ships Nov 22. Check the computer behind an infected KVM.

Sources: [GL.iNet Security Notice 2026-11-20: Router and KVM Security Incident (last updated Nov 21, 2026 UTC)](https://www.gl-inet.com/en-us/blogs/blog/glinet-security-notice-2026-11-20)
