Which versions of stellar-api-core are malicious?

The following npm versions of stellar-api-core are flagged malicious: 1.0.5. Treat any of these as compromised.

How do I remediate stellar-api-core if I installed it?

stellar-api-core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed stellar-api-core — how do I know if it already compromised me?

If stellar-api-core was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is stellar-api-core part of a known attack campaign?

Yes — stellar-api-core is associated with the IN-MAL-2026-015800 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find stellar-api-core across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for stellar-api-core (version 1.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stellar-api-core across your stack and pipelines.

Malicious package

stellar-api-corenpm

stellar-api-core is a confirmed malicious npm package (MAL-2026-13352) that steals credentials and exfiltrates sensitive data (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in stellar-api-core (npm)

MAL-2026-13352

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall stellar-api-core

What this malware does

The package's constructor unconditionally appends a hardcoded Discord user ID (1489655840662093854) to the caller-supplied adminIds list, granting that account persistent admin access to every deployment of the bot. The bot's admin panel dropdown handler (stellar_panel_dropdown -> handleManualRefresh) returns users' Nakama access/refresh tokens as a Discord attachment (token.json), so the injected admin can retrieve installer/user credentials from a running deployment. In addition, two hardcoded Discord webhook URLs (discord.com/api/webhooks/1527809440084922462/... and discord.com/api/webhooks/1527807036350398687/...) receive, without disclosure or opt-out, permanent (maxAge:0, maxUses:0) invite links for every guild the bot is in or joins, plus notifications on each user token add/refresh/delete. The invite exfiltration lets the hardcoded admin join those guilds and then extract user tokens via the admin panel path.

Malicious versions

1 flagged

1.0.5

Indicators of compromise (SHA-256)

fd4c86bebaa61a9aada2c1686d68eb5119025ea4646426ea7da3db4ce4208707

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for stellar-api-core (version 1.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging stellar-api-core across your stack and pipelines.
If you installed it — respond
stellar-api-core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If stellar-api-core was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks stellar-api-core before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. stellar-api-core on npm has been identified as a malicious package (version 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015800

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks stellar-api-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database