We’ve been digging through the
#React RCE mess for two days now, trying to get at least some visibility into what’s going on out there. None of this is easy to detect, and most signals vanish in memory before you can even look at them.
My teammate
@_swachchhanda_ put together a pair of
#Sigma rules that cover the one thing that reliably shows up when someone actually executes code on a Node.js server -> child processes. One rule for Linux, one for Windows. It’s not a silver bullet, just one of the few angles that makes sense right now.
We pushed all our
#YARA and
#Sigma signatures for the React RCE cases as well, and contributed the Sigma rules upstream:
github.com/SigmaHQ/sigma/pul…
This whole situation shows how much attack surface lives in places many of us didn’t think about before. I expect we’ll see more of this class of issues now that people realize what’s possible.