seekcode
Seek Code — a terminal-native coding agent powered by DeepSeek models
This report shows the evidence for seekcode@0.4.6. 3 of 4 known versions are blocked or flagged. The newest version, 0.5.0, is allowed. See all versions.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-4667 confirms this npm version as malicious.
Advisory
MAL-2026-4667
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in seekcode (npm)
Details
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.
Source & flagged code
0 flaggedNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to seekcode@0.4.6.
The same advisory and Firewall decision cover 3 recorded versions
0.4.0, 0.4.4, 0.4.6
The versions list below shows the verdict for each recorded version.
- Avoid installing seekcode@0.4.6. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.