# Node-RED deployment and process review

Start with the two Sigma rules. They use conventional webserver and Linux process-creation sources, with no Deception Check event schema. Native hunt starters are provided where public telemetry documentation supports them. These are review leads, not proof of exploitation.

## Start here

1. Identify the Node-RED servers, admin URL prefix, approved deployments, and expected exec nodes. Node-RED's [security guidance](https://nodered.org/docs/user-guide/runtime/securing-node-red) explains admin authentication and transport security. The [configuration reference](https://nodered.org/docs/user-guide/runtime/configuration) describes `httpAdminRoot`; hiding the editor with `disableEditor` leaves admin API endpoints active.
2. Select the source in [COMPATIBILITY.md](COMPATIBILITY.md), replace every `REPLACE_WITH_...` value, and select a bounded time range. For Sigma, configure your backend's normal source and field mappings before conversion.
3. Review POST requests to `/flows` or a prefixed admin path. The [API reference](https://nodered.org/docs/api/admin/methods/post/flows/) defines this as setting the active configuration. Success is HTTP 200 for API v2 or 204 for v1. The rules retain other statuses and missing status values so rejected and incompletely logged attempts remain visible. A response code alone does not establish authorization, malicious intent, or executed flow content.
4. On the same verified server, inspect direct shell or downloader children of `node` or `nodejs`. Check the parent command line to establish that it is Node-RED. Compare the user, command lines, time, and deployment record. Investigate unexpected activity through your normal incident process.

## Interpret the leads

The process lead covers direct children named `sh`, `bash`, `dash`, `zsh`, `ksh`, `curl`, or `wget`. Legitimate exec nodes, package managers, and maintenance can match. A shell match does not prove a download; a downloader match does not prove a completed transfer. This behavior hunt is broader than the activity described in [VulnCheck's November 2 report](https://www.vulncheck.com/blog/exploitation-targeting-node-red), and does not attribute results to that campaign.

The web rule needs a parsed method and a path without query parameters. The native raw-log searches support NCSA common/combined request-line formatting, including an optional query string, and extract fields at search time. All web leads accept a path prefix and an optional trailing slash; scope them to Node-RED because other applications can also have `/flows` routes. Confirm whether your proxy logs the external or rewritten path. Encoded, malformed, or unusually formatted paths need separate investigation.

## Coverage and validation limits

Process histories need an enabled sensor, retained process starts, and parent identity. Missing required method, path, parent image/name, or child image/name cannot satisfy the corresponding lead. Missing command lines reduce context. A quiet query can reflect absent ingestion, expired retention, excluded containers, or an unsupported appliance. Direct-child matching misses renamed binaries, other interpreters, grandchildren, and activity entirely inside Node.js. Correlate through stable device and process identities where available; a raw PID or a nearby timestamp alone does not establish a process relationship or causal sequence.

Safe local fixtures checked the final Sigma predicates, raw request extraction, and native filter semantics. Sigma was parsed with pySigma 2.0.2 and converted with its Splunk backend 3.0.0; generated fields and conditions were inspected and locally fixture-checked. The conversion used no source mapping pipeline and is not a deployable query. Native query logic was tested locally, not compiled by each vendor engine. No vendor or customer tenant was queried, and no flow or payload was executed. Validate source coverage and native syntax in your own authorized environment before turning a hunt into an alert.

See [REFERENCES.md](REFERENCES.md) for telemetry and syntax sources, and [catalog.json](catalog.json) for the file catalog.
