registry / Data exfiltration / stellar-api-safe
stellar-api-safe
The official Stellar API wrapper for Nakama token management bots.
This report shows the evidence for stellar-api-safe@1.0.8, the only known version.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms a concrete, externally directed metadata-exfiltration channel rather than only scanner heuristics. It is runtime-gated but uses a hard-coded recipient unrelated to required bot configuration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Consumer instantiates StellarBot and calls start(); Discord token commands or refresh events then occur.
Impact
Unconsented disclosure of Discord usernames, user IDs, and token-operation metadata to an external webhook.
Mechanism
hard-coded webhook telemetry of token-management activity
Attack narrative
The exported bot must be explicitly started, then accepts user tokens and refresh tokens. Although refresh requests go to the consumer-configured backend, every add/delete/refresh/failure event is also posted to an embedded Discord webhook controlled outside the consumer's configuration. Those posts disclose user identifiers and token-management activity without a way for the consumer to select or disable the recipient.
AI rationale
Source inspection confirms a concrete, externally directed metadata-exfiltration channel rather than only scanner heuristics. It is runtime-gated but uses a hard-coded recipient unrelated to required bot configuration.
Evidence
package.jsonindex.jsREADME.mddata/<userId>_token.json
Network endpoints2
discord.com/api/webhooks/1527807036350398687/3sPFiOKr2BotMU2y3-ZRXkdosQ4zkoF_ZazcKCFXrMztR-Toducmm1L2xN7ezS3Vn806${config.apiUrl}/refresh
Decision evidence
public snapshotAI called this Malicious at 90.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js hard-codes an external Discord webhook.
- Runtime posts user names/IDs and token-operation events to that webhook.
- The webhook destination is not configurable by the package consumer.
- README documents logging but not the hard-coded third-party recipient.
Evidence against
- package.json has no lifecycle scripts.
- Import only defines and exports StellarBot; execution requires bot.start().
- Refresh tokens are sent only to the consumer-supplied apiUrl as stated bot functionality.
- No shell execution, dynamic code loading, or environment harvesting found.
Behavioral surface
FilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
2 flagged · loading sourceindex.jsView file
14const path = require('path');
L15: const axios = require('axios');
L16:
...
L37:
L38: this.dataDir = path.join(process.cwd(), 'data');
L39: if (!fs.existsSync(this.dataDir)) fs.mkdirSync(this.dataDir, { recursive: true });
...
L46: logToServerWebhook(message) {
L47: // axios.post(this.serverWebhook, { content: message }).catch(() => {});
L48: }
...
L189: await interaction.deferReply({ ephemeral: true });
L190: const oldData = JSON.parse(fs.readFileSync(filePath, 'utf8'));
L191: const result = await this.callBackendAPI(oldData.refresh_token);
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
index.jsView on unpkg · L1414Trigger-reachable chain: manifest.main -> index.js
L14: const path = require('path');
L15: const axios = require('axios');
L16:
...
L37:
L38: this.dataDir = path.join(process.cwd(), 'data');
L39: if (!fs.existsSync(this.dataDir)) fs.mkdirSync(this.dataDir, { recursive: true });
...
L46: logToServerWebhook(message) {
L47: // axios.post(this.serverWebhook, { content: message }).catch(() => {});
L48: }
...
L189: await interaction.deferReply({ ephemeral: true });
L190: const oldData = JSON.parse(fs.readFileSync(filePath, 'utf8'));
L191: const result = await this.callBackendAPI(oldData.refresh_token);
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
index.jsView on unpkg · L14Findings
2 Critical2 Medium4 Low
CriticalCredential Exfiltrationindex.js
CriticalTrigger Reachable Dangerous Capabilityindex.js
MediumNetwork
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to stellar-api-safe@1.0.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing stellar-api-safe@1.0.8. 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.