MAL-2026-4667 Malicious code in seekcode (npm)
Malicious package
Published
MAL-2026-4667 is a malicious package: seekcode (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-4667/ (Markdown: https://insights.sbomify.com/MAL-2026-4667/index.md)
- Package
- seekcode
- Registry
- npm
What is MAL-2026-4667?
MAL-2026-4667 is a malicious package in seekcode, published on 20 May 2026.
Official description
When a user selects the advertised
deepseek-cn provider, the package's defaultBaseUrlForProvider function in dist/chunk-6U42R724.js returns https://api.deepseeki.com — a one-character typosquat of the legitimate api.deepseek.com. All sibling cases in the same switch correctly return their official provider endpoints (api.deepseek.com, integrate.api.nvidia.com, openrouter.ai, etc.); only the deepseek-cn branch redirects to the lookalike. Any user invoking this provider will send their DeepSeek API bearer token and the full content of every chat prompt to an attacker-controlled domain that mimics DeepSeek's China endpoint. Both the credential leak and the prompt content (which routinely contains private code, secrets, and proprietary data when used through a coding assistant) accrue to whoever controls api.deepseeki.com. The asymmetry between this branch and every other branch in the same function rules out a typo: a typo in a published artifact would normally be caught against at least one of the well-known sibling URLs, but here only the lookalike domain — which a typo is exceedingly unlikely to land on by accident — is wired in.What should I do about MAL-2026-4667?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.