spacecode@2.17.16
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 4h ago · by lpm-firewall-aiSource inspection confirms an automatic transfer of ANTHROPIC_API_KEY to the package-selected backend without recipient-specific consent. This supports blocking for credential exfiltration; the prompt-fetch opt-out does not change the default transfer path.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Starting the REPL with ANTHROPIC_API_KEY set and prompt fetching enabled, which is the default.
Impact
The backend receives the user’s Anthropic API credential, creating a risk of unauthorized use.
Mechanism
The key resolver accepts ANTHROPIC_API_KEY, and automatic prompt loading sends the resolved value as a bearer token and x-api-key header to the backend prompt endpoint.
Attack narrative
When the REPL starts, it loads prompt templates automatically. Its key resolver accepts ANTHROPIC_API_KEY, and the prompt request sends the resolved key to the package’s backend service. This is a concrete credential transfer to a recipient outside the key’s intended service.
AI rationale
Source inspection confirms an automatic transfer of ANTHROPIC_API_KEY to the package-selected backend without recipient-specific consent. This supports blocking for credential exfiltration; the prompt-fetch opt-out does not change the default transfer path.
Evidence
dist/repl.mjs
Network endpoints1
backend.spacecode.app/api/prompts
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The REPL accepts ANTHROPIC_API_KEY as an API key.
- On REPL startup, prompt loading runs automatically and sends the key in authorization headers to the backend prompt endpoint.
- The endpoint defaults to the package’s backend service; no recipient-specific consent guard appears in the transfer path.
Evidence against
- The prompt request can be disabled with SPACECODE_PROMPTS=off, but it is enabled by default.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Oversized source lightweight scan
dist/repl.mjs
Source & flagged code
12 flagged · loading sourcedist/index.jsView file
1122try {
L1123: const execAsync = (0, import_util.promisify)(import_child_process.exec);
L1124: const options = {};
High
1122try {
L1123: const execAsync = (0, import_util.promisify)(import_child_process.exec);
L1124: const options = {};
High
•Manifest-reachable source captures an API credential, sends it to a fixed unofficial gateway, and persists that redirection in agent or shell configuration.
dist/index.js:
baseUrl;
constructor(baseUrl, token) {
this.baseUrl = baseUrl ?? process.env.SPACECODE_API_URL ?? DEFAULT_API_URL;
const url = `${this.baseUrl}${path6}`;
headers["Authorization"] = `Bearer ${this.token}`;
throw new AuthError("Authentication failed. Please check your API key or run a command to re-authenticate");
const response = await fetch(`${this.baseUrl}/health`, {
const url = `${this.baseUrl}/api/auth/exchange`;
High
Credential Redirect Persistence
Manifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/index.jsFindings
9 High5 Medium4 Low
HighChild Processdist/index.js
HighShelldist/index.js
HighCredential Redirect Persistencedist/index.js
HighRemote Agent Bridgedist/index.js
HighCross File Remote Execution Contextdist/index.js
HighKnown Malware Source Similaritydist/index.js
HighKnown Malware Source Similaritydist/repl.mjs
HighKnown Malware Source Similaritydist/mcp/index.js
HighKnown Malware Source Fingerprint Signaturedist/index.js
MediumNetwork
MediumEnvironment Vars
MediumOversized Source Filedist/repl.mjs
MediumOversized Cli Entrypointdist/repl.mjs
Affected versions and remediation
This report applies to spacecode@2.17.16.
See all versions of spacecode for other recorded verdicts.
- Avoid installing spacecode@2.17.16. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.