My current assumption is that (apart from an always suspected malicious action) it could have been a glitch in Microsoft Sysinternals’ Process Explorer’s “Replace Task Manager” option, even though I couldn’t recreate the issue once it was resolved. Fingers-crossed that fix will still work...