@testsmith/api-spector-agent@0.7.6
API Spector private runner: monitor internal/local APIs the cloud cannot reach, with no inbound connections.
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe expression evaluation creates a real sandbox escape risk when a crafted monitor reaches the runner, so this warrants a warning. The inspected source does not show an active attack in the package's default startup path.
Decision evidence
public snapshot- The package exposes dist/index.cjs as its command-line and module entrypoint.
- Template expressions are evaluated with Node's VM using host-provided faker and dayjs objects.
- The agent polls the configured application endpoint for due monitors and passes each monitor's request into the request runner.
- The request URL is built from monitor data through the interpolation path.
- The risky path requires the running agent to process a crafted monitor expression; no active exploit or file change is established by the inspected source.
Source & flagged code
6 flaggedSource contains an obfuscated payload loader that reconstructs and executes hidden code.
dist/index.cjsView on unpkg · L247A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/index.cjsView on unpkgFindings
Affected versions and remediation
This report applies to @testsmith/api-spector-agent@0.7.6.
See all versions of @testsmith/api-spector-agent for other recorded verdicts.
- Review the evidence and your use of @testsmith/api-spector-agent@0.7.6 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.