# RunShield by Imunify (Node.js) > RunShield runs inside Node.js applications on a server. It blocks SQL and NoSQL injection at the > database driver, fixes known-vulnerable npm packages in memory with virtual patches, refuses to load > confirmed malicious npm releases, and reports which vulnerable versions an application actually loads. > This site lists every known vulnerability in npm packages, and an API that checks a project's > dependencies against them, with what RunShield does about each. > RunShield is in early access: it is new and still changing, and it starts in report mode. Advisory data of 2026-11-17; feed built 2026-11-17T15:54:37.209Z. Sources: GitHub Advisory Database / OSV, NVD, Node.js security releases. ## Check a project's dependencies POST https://runshield.com/api/v1/check Content-Type: application/json Body, one of: - {"lockfile": } - {"packages": ["lodash@4.17.20", "axios@0.21.1"]} GET https://runshield.com/api/v1/check?packages=lodash@4.17.20,axios@0.21.1 does the same for a short list. At most 5000 packages per call; bodies up to 20 MB. No authentication. Nothing is stored. Response: { "checked": 412, // distinct name@version pairs "vulnerable": 9, // pairs with at least one advisory "results": [ { "package": "lodash@4.17.20", "advisory": "GHSA-35jh-r3h4-6jhm", "cve": "CVE-2021-23337", "title": "Command Injection in lodash", "severity": "high", "cvss": 7.2, "exploit": true, "affected": "<4.17.21", "fixed_in": "4.17.21", "runtimeguard": "virtual-patch" | "blocked" | "detected" | "none", "url": "https://github.com/advisories/GHSA-35jh-r3h4-6jhm" } ], "malicious": [{"package": "event-stream@3.3.6", "incident": "..."}] } runtimeguard values (RunShield coverage; the field keeps its earlier name): - virtual-patch: RunShield fixes the vulnerable code in memory for the affected versions. - blocked: an injection attack we reproduced in our lab and block at the database call (block mode). - detected: RunShield reports the vulnerable version when the application loads it. - none: not covered yet. GET https://runshield.com/api/v1/advisory?id= returns one advisory with its affected ranges and virtually patched versions. ### How to use it on a project 1. Read package-lock.json (run `npm install --package-lock-only` if there is none) and POST it. 2. For each result, find where the project uses the package (imports, the vulnerable function) and say whether the vulnerable path is reachable from the application's input, with file and line. 3. Report: package@version, advisory, severity, fixed version, RunShield coverage, recommended action. 4. Do not change code or dependencies without the user's confirmation. ## Install RunShield on a server Requirements: - root on the server (every step below runs with sudo); - x86-64 Linux with systemd; - Node.js 16, 18, 20, 22 or 24 for the applications; - npm and curl. On servers with Imunify360 or ImunifyAV, Imunify installs RunShield itself; do not install it by hand there. One command installs the latest release, or upgrades an installed one, and turns RunShield on in report mode: https://runshield.com/install.sh. It checks the requirements above, downloads the release from https://runshield.com/release/, verifies its sha512, runs `npm i -g` and the package's `runshield enable` (`upgrade` if an older release is on), and restarts nothing. A release before 0.5 (the `imunify-rasp` command) is not upgraded in place: `runshield enable` removes it and RunShield takes its place with default settings, and applications that were running stay on the removed agent, which no longer reports, until they restart. It then lists the Node.js runtimes and applications on the server (systemd units, pm2 apps, containers, processes started by hand) and, for each one RunShield is not attached to yet, the file to change and the commands that attach it. Show the user that list and ask before changing any of them. The script sends nothing about the server or its run anywhere: the release is all it asks this site for. Steps (show the user the script and ask before running it as root): curl -fsSLO https://runshield.com/install.sh cat install.sh # show the user what will run as root sudo sh install.sh On a server you administer yourself the same in one line: `curl -fsSL https://runshield.com/install.sh | sudo sh`. Applications pick RunShield up when they restart: eval "$(sudo runshield env)" # then start the app from this shell, or: sudo runshield env --systemd # | --pm2 | --docker for apps under a service manager Then check: sudo runshield status # every application process should show as protected RunShield starts in report mode: it records attacks and does not block them. Block mode is the server owner's decision: `sudo runshield mode block && sudo runshield reload`. Turn it off with `sudo runshield disable`, remove it with `sudo runshield uninstall`. ## Pages - https://runshield.com/feed: every known vulnerability in npm packages, with its severity and exploit - https://runshield.com/malicious: malicious npm releases RunShield refuses to load - https://runshield.com/check: the same check in the browser