The scanner findings resolve to tripwire path literals, command-injection signatures, and a caller-configured Upstash transport. Runtime detection requests use the configured WebDecoy API and key, which is consistent with the package’s stated purpose; no install-time or unrelated credential theft behavior was found.
Static reason
No blocking static signals were detected.
Trigger
A consumer configures and invokes the exported middleware; optional rate limiting runs when configured.
Impact
Expected request metadata is sent to the configured protection service; configured rate-limit data is sent to the configured Upstash endpoint.
Mechanism
Detection calls use the configured WebDecoy API URL and key. Upstash calls use the configured URL and token. The scanner’s credential and shell matches are detection rules or path literals.
Network endpoints2
Configured WebDecoy apiUrlConfigured Upstash URL