# MAL-2026-3641: Malicious code in camelotlabs-core (npm)


- **Type:** Malicious package
- **Package:** `camelotlabs-core` (npm)
- **Published:** 7 May 2026
- **Also known as:** GHSA-pf82-f9wr-54vx

## What is MAL-2026-3641?

MAL-2026-3641 is a malicious package in camelotlabs-core, published on 7 May 2026. 

### Official description

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`.

camelotlabs-core@0.0.0-stage is a two-file npm package with a pre-release stage version identifier. No install lifecycle scripts, no network activity, no filesystem access to installer-owned secret paths, no credential handling, and no code-fetch-and-execute patterns were observed in the shipped contents. The package appears to be a placeholder or staging release with no functional payload.

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.

## What should I do about MAL-2026-3641?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-3641 is a malicious package: camelotlabs-core (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-3641/ (Markdown: https://insights.sbomify.com/MAL-2026-3641/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-3641

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-3641/
Summaries are generated and may contain mistakes; the official description above is the record.