npm

The stellar-api-core npm Supply Chain Attack

Updated 18 Nov 2026 · Incident date 18 Jul 2026

Versions 1.0.3 to 1.0.7 of the npm package stellar-api-core add a hardcoded Discord admin that can pull users' Nakama tokens, says OpenSSF record MAL-2026-13352.

Versions 1.0.0 to 1.0.2 do not carry the hardcoded admin, says the record. The registry lists eight releases, 1.0.0 to 1.0.7, from 17 and 18 July 2026.

What happened

Version 1.0.3 went up on npm at 04:08 UTC on 18 July 2026. OpenSSF record MAL-2026-13352, credited to Amazon Inspector and wormsign, reports these actions:

  • The constructor adds Discord user ID 1489655840662093854 to the caller's admin list.
  • The admin panel handler returns users' Nakama access and refresh tokens as a token.json attachment.
  • From 1.0.5, two hardcoded Discord webhooks receive permanent invite links for every guild the bot is in.
  • The same webhooks receive a notice on each user token add, refresh or delete.
  • GitHub published malware advisory GHSA-x5g6-2wvp-v57q on 18 November 2026. npm replaced the package with a security holder the same day.

The code was unavailable for inspection because npm no longer serves it. These findings come from the record.

Affected versions

  • 1.0.3 and 1.0.4: hardcoded admin and token path, says MAL-2026-13352.
  • 1.0.5, 1.0.6 and 1.0.7: the same, plus the guild invite exfiltration.
  • 1.0.0 to 1.0.2: the record says they do not inject the admin.
  • GitHub lists every version (>= 0) as affected.

Indicators of compromise

  • Discord user ID: 1489655840662093854
  • Webhook ID: 1527809440084922462
  • Webhook ID: 1527807036350398687
  • index.js SHA-256 in 1.0.5 to 1.0.7: d474179bc987546968fb83896e91ffce1089efd11a894ae58366993cee79c943

How to check

In a project folder, list every copy of the package.

npm ls stellar-api-core --all

To search a running bot's files for the hardcoded admin, search for its ID.

grep -rn "1489655840662093854" node_modules

What to do now

  1. If you find 1.0.3 or later, treat that computer as fully compromised. GitHub gives this advice.
  2. From a different computer, rotate every secret and key the exposed computer stored, including the bot token and users' Nakama tokens.
  3. Remove the package. GitHub warns that removal does not guarantee that all malicious software is gone.
  4. Revoke the bot's guild invite links and remove unknown admins.

What Vigilance would show

These examples show an install hold and the corresponding owner report.

Example install message

Vigilance blocked `stellar-api-core` 1.0.3. This version is too new or changed in a way Vigilance must check first.

Example owner report

Bad update

stellar-api-core 1.0.3

The package gives a stranger's Discord account admin rights in your bot, and that account can download your users' login tokens.

See what to do now.

No security team? See who reads the alert.

Frequently asked questions

Is stellar-api-core safe to use?

No. GitHub flags every version as malware, and npm now serves only a security holder.

What can the hidden admin in stellar-api-core do?

MAL-2026-13352 says the admin can pull users' Nakama tokens through the bot's admin panel. The invite links let that admin join the bot's guilds.

Sources

  1. api.osv.dev/v1/vulns/MAL-2026-13352
  2. github.com/advisories/GHSA-x5g6-2wvp-v57q
  3. registry.npmjs.org/stellar-api-core

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · npm supply chain attacks · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library