hunt-nodejs

Validates Node.js, Express, Fastify, and NestJS server boundaries through evidence-gated black-box probing.

10|3|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-nodejs-baiqigo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-nodejs
Source: https://github.com/baiqigo/baiqi-redteam-lab/tree/main/.agents/skills/hunt-nodejs
Command: npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-nodejs-baiqigo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security testers assessing Node.js backends often lack a disciplined, evidence-driven process, leading to false positives from scanner hits, npm package guesses, or frontend JavaScript misread as server-side findings. This Skill enforces an authorization-first, single-variable probing methodology for Node.js, Express, Fastify, and NestJS targets so every reported issue is backed by server-side oracle evidence. ## Core Features & Use Cases - Framework Fingerprinting: Confirms runtime, framework, and version via response headers, error stacks, build artifacts, and deployment metadata before any testing. - Evidence-Gated Probing: Applies a strict baseline → single-variable probe → post-baseline → oracle → evidence loop for parser, path, and authorization differentials. - Routing & Escalation Discipline: Routes prototype pollution, command injection, SSTI, upload, and dependency findings to dedicated specialist Skills, and CVEs to the bb-methodology workflow. - Use Case: During an authorized engagement against an Express API, use this Skill to confirm the stack version, map JSON/query/body parsers and static paths, then run safe differential probes on your own objects while treating WAF blocks and scanner hits as inconclusive. ## Quick Start Use the hunt-nodejs skill to plan an evidence-gated, authorized validation path against my in-scope Node.js target.

Frequently Asked Questions about hunt-nodejs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test a Node.js API for security issues in a black-box engagement?

Start by fingerprinting the framework and version from response headers, error stacks, or deployment metadata, then map parsers, static paths, and routes. Run single-variable probes against your own objects and only accept findings confirmed by a server-side oracle.

How to fingerprint Express, Fastify, or NestJS servers during reconnaissance?

Look for trigger signals such as Express headers, Fastify markers, Nest markers, package metadata, and Node stack traces in error responses. Public build artifacts and official deployment metadata also confirm framework and version before testing begins.

Does this Node.js testing approach work without authorization?

No. The methodology requires declared authorization, locked scope, and an established host, identity, and path baseline before any probing. It only uses your own accounts, objects, domains, and approved request rates.

Why are scanner hits and WAF blocks treated as inconclusive in Node.js testing?

Scanner hits, WAF responses, captchas, timeouts, and single errors do not prove a server-side boundary failure. Only a confirmed Node stack meeting documented preconditions or a harmless server-side oracle showing boundary failure counts as valid evidence.

What are the limitations of black-box Node.js boundary validation?

It stops short of installing dependencies, executing commands, polluting shared objects, or reading environment variables. Prototype pollution, command injection, SSTI, uploads, and dependency issues are handed off to dedicated specialist workflows.