Pervasive System

Sometimes when looking at a module list (lmv WinDbg command) we see the whole presence of this pattern. It is not just a module that does function (Volume 1, page 469) and / or message (page 76) hooking but the whole system of modules from a single vendor that is context-aware (for example, reads its configuration from registry) and consists of several components that communicate with other processes. The penetrated system is supposed to add some additional value or to coexist peacefully in a larger environment. The system thus becomes coupled strongly (Volume 1, page 419) and / or weekly (page 60) with other processes it was never intended to work with as opposed to intended module variety (Volume 1, page 310). At one extreme, modules from pervasive system can be ubiquitous (Volume 4, page 94) and, at the other end, hidden (Volume 2, page 339). In such cases troubleshooting consists of the total removal of the pervasive modules and, if the problem disappears, their exclusion one by one to find the problem component.