Malicious npm package detection

Several npm packages were of malicious nature. npm has since removed them from their registry, but the packages could still be installed on a host.

Following packages are affected: - npm-script-demo - pandora-doomsday - botbait - d3.js - jquery.js - mariadb - mysqljs - node-sqlite - nodesqlite - sqlite.js - sqliter - node-fabric - fabric-js - nodefabric - sqlserver - mssql.js - nodemssql - gruntcli - mssql-node - babelcli - tkinter - node-tkinter - node-opensl - node-openssl - openssl.js - opencv.js - node-opencv - ffmepg - nodeffmpeg - nodecaffe - nodemailer-js - nodemailer.js - noderequest - crossenv - http-proxy.js - proxy.js - mongose - shadowsock - smb - nodesass - cross-env.js - cofee-script, cofeescript, coffescript, coffe-script - jquey - discordi.js - hooka-tools - getcookies - nothing-js - ladder-text-js - boogeyman - flatmap-stream

Checks if a malicious npm package is present on the target host.

- Delete the package - Clear your npm cache - Ensure it is not present in any other package.json files on your system - Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.