registry / @evomap/evolver-proxy / 2.0.34

@evomap/evolver-proxy@2.0.34

系统级 mailbox/hub 同步 daemon (Node)

AI Security Review

scanned 26d ago · by lpm-firewall-ai

When the user runs the LLM proxy, it accepts LLM requests, reads upstream credentials from its environment, and records traces. Opaque runtime modules can enqueue encrypted trace records for outbound delivery, so the exact data-handling behavior cannot be independently verified.

Static reason

One or more suspicious static signals were detected.

Trigger

An explicit invocation of evolver-llm-proxy or evolver-proxy.

Impact

Prompts, responses, and credentials handled by the proxy could be exposed or forwarded beyond the expected upstream service.

Mechanism

LLM request proxying with encrypted trace capture and mailbox delivery.

AI rationale

This is not confirmed malware because it has no lifecycle hook and activation requires an explicit CLI command. The pervasive obfuscation around a credential-handling trace proxy leaves a material unresolved data-exposure risk.

Evidence

dist/llm/traceEnvelope.jsdist/llm/traceSink.d.tsdist/bin/evolver-llm-proxy.jsdist/llm/traceSink.jsdist/llm/traceBackfill.jsdist/llm/upstream.js

Network endpoints4

api.anthropic.comapi.openai.com/v1generativelanguage.googleapis.com127.0.0.1:11434

@evomap/evolver-proxy@2.0.34

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Source & flagged code