Which versions of camelotlabs-worker are malicious?

The following npm versions of camelotlabs-worker are flagged malicious: 0.0.0-stage. Treat any of these as compromised.

How do I remediate camelotlabs-worker if I installed it?

camelotlabs-worker 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.

I already installed camelotlabs-worker — how do I know if it already compromised me?

If camelotlabs-worker 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.

Is camelotlabs-worker part of a known attack campaign?

Yes — camelotlabs-worker is associated with the GHSA-4mgg-vrvh-32xg, IN-MAL-2026-022190 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find camelotlabs-worker across my projects, lockfiles, and CI pipelines?

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

Malicious package

camelotlabs-workernpm

Advisory published May 7, 2026Updated Oct 29, 2026

camelotlabs-worker is a confirmed malicious npm package (MAL-2026-3644) 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-worker (npm)

MAL-2026-3644

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall camelotlabs-worker

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.

The package consists of two files with no a static rule matches and no traced installer-harm behavior. No lifecycle scripts, no outbound network calls to attacker-controlled destinations, no credential or environment reads, no filesystem persistence, and no code fetched or executed from remote sources are observable. The '0.0.0-stage' version string and minimal content suggest a staging or placeholder release rather than a functional library.

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)

3abf4b8acb69887cbb8f7cd9c78406dfc0f1211946e5b9db34aae46840b9e087

0e0782db9a7d33e51ab9524a42a292ca4079dbd07ae25c7fb57a51877647fa98

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for camelotlabs-worker (version 0.0.0-stage).
If you installed it — respond
camelotlabs-worker 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.
Did it already run?
If camelotlabs-worker 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-worker 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-4mgg-vrvh-32xgIN-MAL-2026-022190

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database