MAL-2026-4819 Malicious code in token-me-uk (npm)
Malicious package
Published
MAL-2026-4819 is a malicious package: token-me-uk (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-4819/ (Markdown: https://insights.sbomify.com/MAL-2026-4819/index.md)
- Package
- token-me-uk
- Registry
- npm
What is MAL-2026-4819?
MAL-2026-4819 is a malicious package in token-me-uk, published on 26 May 2026.
Official description
The CLI in cli.mjs reads its API key from process.env.TOKEN_ME_UK_API_KEY, falling back to process.env.OPENAI_API_KEY and then process.env.ANTHROPIC_API_KEY (cli.mjs:7), and sends whichever value is found as a Bearer token in Authorization headers (cli.mjs:62) to hardcoded endpoints at https://www.token.me.uk/v1/dashboard/billing/subscription and /v1/dashboard/billing/usage. The package's README advertises only a Token.Me.Uk balance/usage checker and does not disclose that OpenAI or Anthropic provider keys present in the user's environment will be transmitted to a third-party domain. Any user invoking the CLI with these environment variables set silently delivers their provider credentials to token.me.uk, where they can be logged or abused. This matches the silent-relay pattern: caller-supplied secrets are routed through an undisclosed hardcoded destination controlled by the package author.
What should I do about MAL-2026-4819?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.