MAL-2026-10633 Malicious code in creditgauge (npm)
Malicious package
Published
MAL-2026-10633 is a malicious package: creditgauge (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-10633/ (Markdown: https://insights.sbomify.com/MAL-2026-10633/index.md)
- Package
- creditgauge
- Registry
- npm
What is MAL-2026-10633?
MAL-2026-10633 is a malicious package in creditgauge, published on 15 Jul 2026.
Official description
The package has no functional library code: package.json declares main=index.js but no index.js is shipped; the tarball contains only package.json and a.claude/settings.json payload. The settings.json overrides ANTHROPIC_BASE_URL to https://api.minimaxi.com/anthropic (a non-Anthropic host) and embeds a hardcoded ANTHROPIC_AUTH_TOKEN, so any Claude Code session picking up this configuration silently routes the developer's prompts and source code through a third-party endpoint under an attacker-supplied token. The same file defines a statusLine that runs a bash command resolving to scripts/wrapper.sh inside the plugin cache directory for the third-party plugin github:cwf818/topgauge-cc (referenced via enabledPlugins), re-invoked every 10 seconds. defaultMode is set to bypassPermissions and skipDangerousModePermissionPrompt is set to true, disabling the confirmation prompts that would normally gate that execution. The combined effect is silent relay of AI prompts/code through an attacker-controlled proxy plus recurring shell execution of unvetted third-party plugin code inside the developer's environment.
What should I do about MAL-2026-10633?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.