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

camelotlabs-sdknpm

Advisory published Updated

camelotlabs-sdk is a confirmed malicious npm package (MAL-2026-3642) that steals credentials and exfiltrates sensitive data (malicious version 0.0.0-stage). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in camelotlabs-sdk (npm)

MAL-2026-3642
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall camelotlabs-sdk

What this malware does

Five packages (camelotlabs-sdk, camelotlabs-core, camelotlabs-config, camelotlabs-worker, and camelotlabs-utils) were published to the public npm registry at version 99.0.0 by the actor madman0619 as a dependency confusion attack targeting the internal npm packages of Camelot Labs. The inflated version number causes npm to prefer the public malicious package over any internally-hosted version of the same name. All five packages carry an identical payload designed to exfiltrate credentials from Cloudflare Workers projects using Upstash Redis and HMAC signing keys.

On installation the preinstall script executes index.js, which collects hostname, platform, working directory, and environment variables whose names match patterns for API keys, tokens, secrets, HMAC signing keys, Upstash/Redis credentials, Vercel and Cloudflare environment bindings, and database connection strings. It also reads and exfiltrates .env, .env.production, .env.local, wrangler.toml, wrangler.json, and wrangler.jsonc files from the working directory and its parents. All collected data is sent via HTTP POST to the C2 server at http://82.221.101.203:9999/exfil.

Package camelotlabs-sdk at version 0.0.0-stage contains two files with no behaviors indicative of a supply-chain attack. No install-time or import-time network fetch-and-execute, no credential or environment harvesting, no silent-relay of caller data to a hardcoded destination, no backdoor or persistence mechanism, and no dependency-chain dropper structure is present. The version string and minimal content are consistent with a staging or placeholder publish.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
0.0.0-stage

Indicators of compromise (SHA-256)

3bfb238877326aafceb45427d1ac0efdc9a270365ccf825436021256880abe59
d72bafa1cc318f7cf5e23a97214fe71d44d47f5fc9c7aa25640640a3b0870344

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for camelotlabs-sdk (version 0.0.0-stage).

  2. If you installed it — respond

    camelotlabs-sdk 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 camelotlabs-sdk 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. camelotlabs-sdk on npm has been identified as a malicious package (version 0.0.0-stage flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wx8x-c4rg-8rg7IN-MAL-2026-022188

References

Credits

  • Amazon Inspector · finder
  • SafeDep · finder

Detect & block this

O3 blocks camelotlabs-sdk-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

camelotlabs-sdk (npm) malicious package — MAL-2026-3642 | O3 Security