Which versions of token-me-uk are malicious?

The following npm versions of token-me-uk are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate token-me-uk if I installed it?

token-me-uk 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 token-me-uk — how do I know if it already compromised me?

If token-me-uk 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 token-me-uk part of a known attack campaign?

Yes — token-me-uk is associated with the IN-MAL-2026-004916 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 token-me-uk 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 token-me-uk (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging token-me-uk across your stack and pipelines.

Malicious package

token-me-uknpm

Malicious code in token-me-uk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4819

Immediate action

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

npm uninstall token-me-uk

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2a058b653e7a491fdf0c9128b4d2d408c2cdac6a1784adc5f02a0975a0e669eb

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 token-me-uk (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging token-me-uk across your stack and pipelines.
If you installed it — respond
token-me-uk 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 token-me-uk 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 token-me-uk 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. token-me-uk on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004916

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks token-me-uk-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