NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

cosmosdb-servernpm

Advisory published Updated

cosmosdb-server is a confirmed malicious npm package (MAL-2026-4537) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cosmosdb-server (npm)

MAL-2026-4537
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall cosmosdb-server

What this malware does

Package squats the unscoped name cosmosdb-server, targeting users who mistype npx cosmosdb-server instead of the scoped @vercel/cosmosdb-server. The package.json declares bin: {"cosmosdb-server": "./index.js"} and self-describes as a 'bin-mismatch PoC' for the Vercel package. When invoked (via npx, bin execution, or require()), index.js collects os.hostname(), process.cwd(), process.platform, process.arch, and a timestamp and POSTs them to a hardcoded endpoint at https://callback-monitor.cyb3rsh4ykh.workers.dev/c, controlled by the package author. The 'security research / responsible disclosure' framing in the description does not constitute installer consent — the package is published live on the public registry under a name designed to capture mistyped invocations, and victims have no opportunity to opt out before their host identity and working-directory path are exfiltrated. Combination of (a) ≤2-edit name confusion against a scoped Vercel package, (b) hardcoded attacker-controlled exfil endpoint, and (c) immediate-on-execution data collection meets the typosquat-with-installer-harm threshold.

Malicious versions

2 flagged
0.0.10.0.2

Indicators of compromise (SHA-256)

925077d4c86616920b1ad20f2342df7473d9504764582235049e78eed9189a76
bd70e10e2c7d65e7513de4b24cf12a84b72c2b9bc60c308193d16e556579cbc8
92604ddb032b222715131556ae2bd43c107849724e592697f99782131d461e0c

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for cosmosdb-server (2 malicious versions).

  2. If you installed it — respond

    cosmosdb-server 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.

  3. Did it already run?

    If cosmosdb-server was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. cosmosdb-server on npm has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004347IN-MAL-2026-004359IN-MAL-2026-004358

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks cosmosdb-server-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

cosmosdb-server (npm) malicious package — MAL-2026-4537 | O3 Security