spacecode@2.16.24
SpaceCode - launch cloud dev environments with AI coding agents
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe source shows an automatic transfer of an Anthropic credential to the package-selected SpaceCode backend without recipient-specific consent. This is concrete credential disclosure, so the package is malicious.
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
Run the local REPL with ANTHROPIC_API_KEY set and without SPACECODE_PROFILE=off.
Impact
The Anthropic credential is disclosed to a different service than the one it authenticates to.
Mechanism
The REPL treats ANTHROPIC_API_KEY as its API credential, then sends it in authenticated requests to the default SpaceCode backend.
Attack narrative
When the local REPL starts, it prepares and awaits profile data unless the user explicitly disables profile loading. Its credential resolver accepts ANTHROPIC_API_KEY, and the resulting value is sent to the default SpaceCode backend in authenticated profile and prompt requests. This exposes a provider credential to a recipient the user did not select for that credential.
AI rationale
The source shows an automatic transfer of an Anthropic credential to the package-selected SpaceCode backend without recipient-specific consent. This is concrete credential disclosure, so the package is malicious.
Evidence
dist/index.jsdist/repl.mjs
Network endpoints1
backend.spacecode.app
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- The local REPL accepts ANTHROPIC_API_KEY as a fallback credential.
- Profile loading uses that credential by default and passes it to a client for the SpaceCode backend; only an explicit profile-off setting skips this path.
- The profile client sends the credential as bearer authorization to the backend, whose default address is backend.spacecode.app.
- The REPL awaits profile loading, and prompt loading also sends the credential to the backend as bearer authorization and an API key.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Oversized source lightweight scan
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/mcp/index.js
HighKnown Malware Source Similaritydist/repl.mjs
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.16.24.
See all versions of spacecode for other recorded verdicts.
- Avoid installing spacecode@2.16.24. 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.