That particular one can occur if certain binaries aren't fully stripped. If they aren't stripped or optimised, or have debugging info in, then they trigger that test.
On Mon, 15 Dec 2003, Pedro Fernandes Macedo wrote:
In addition, 'short lived' processes may trigger the hidden processes check. It is probably best to run chkrootkit at a lower runlevel, without X and other things running.
Cheers, Michael
