← All advisories
VV-321criticalSupply chain2026-11-19

Malicious npm packages posing as AI SDKs and MCP servers: character-ai-sdk, char-ai-sdk, @mibbp/agent-observer, mrnima-openai-chatgpt-bot and @fdcasj_dfew/md-doc-mcp

Between 18 and 19 November 2026, OSV and GitHub flagged five more AI-themed npm packages as malicious. Two pose as AI persona/memory SDKs (character-ai-sdk, char-ai-sdk) and load large obfuscated blobs as soon as they are imported. @fdcasj_dfew/md-doc-mcp is a Markdown MCP server that probes the Alibaba Cloud metadata service at startup, a republish of the @ifasn doc-MCP packages. @mibbp/agent-observer and mrnima-openai-chatgpt-bot are GitHub malware advisories. Treat any machine that installed or ran one as compromised.

01.

What it is

character-ai-sdk 1.0.0, 1.0.1 (MAL-2026-20196) and char-ai-sdk 1.0.0 (MAL-2026-20195): advertised as AI persona/memory SDKs (char-ai-sdk mentions Bedrock and OpenAI). The main entry re-exports personas.mjs, which imports ./cache-warm.mjs, an obfuscator.io-style blob of about 300 KB, with sibling blobs build-cache.mjs, cache-sweep.mjs and workspaces.js. Decoded strings reference process control, hostname and child-process APIs. character-ai-sdk also ships native cache-probe.node addons built from a VM-detection library (anti-sandbox). Reported by Amazon Inspector.

@fdcasj_dfew/md-doc-mcp 1.0.0, 1.0.1 (MAL-2026-20187): a Markdown toolkit MCP server (md_toc, md_stats, md_table) whose index.js calls fieldCheck() at load, before any MCP message. It requests the Alibaba Cloud instance metadata service (100.100.100.200) for hostname, instance-id, vpc-id, private IPv4 and region, and writes the results to stderr and output/field_check.txt. It matches the earlier @ifasn/md-doc-mcp, @ifasn/mmdd-doc-mcp and @ifasn/ms-doc-mcp packages republished under a new account.

@mibbp/agent-observer (GHSA-2r45-7hg7-w99r / MAL-2026-20254, 19 November) and mrnima-openai-chatgpt-bot (GHSA-xvx7-m3mm-3jpw / MAL-2026-20155, 19 November): GitHub malware advisories, all versions. They don't describe the payload; GitHub's guidance is that any computer that installed or ran them should be considered fully compromised.

MCP servers and agent add-ons are often started with npx straight from a client config, so one launch is enough to run the code with your user's access to files, SSH keys, cloud credentials and API keys.

02.

How to check

  1. Search lockfiles, global installs, the npx cache and MCP client configs (Claude Desktop, Cursor, VS Code, Windsurf) for these five names.
  2. On cloud VMs where md-doc-mcp ran, look for an output/field_check.txt file and review instance metadata access and RAM role credential use.
03.

How to fix

  1. Remove the packages and their MCP config entries, and clear the npx cache.
  2. From a clean machine, rotate every secret that was reachable on an affected one: LLM API keys, cloud credentials (including instance RAM role credentials), GitHub/npm tokens, SSH keys. Rebuilding the machine is the safe option.
  3. Install AI SDKs and MCP servers only from the vendor's documented package name, and pin versions.
grep -rnE '"(character-ai-sdk|char-ai-sdk|@mibbp/agent-observer|mrnima-openai-chatgpt-bot|@fdcasj_dfew/md-doc-mcp)"' package-lock.json pnpm-lock.yaml yarn.lock 2>/dev/null
grep -rlE 'character-ai-sdk|char-ai-sdk|agent-observer|mrnima-openai|md-doc-mcp' ~/.npm/_npx 2>/dev/null
find / -name field_check.txt -path '*output*' 2>/dev/null
04.

Sources

Related on VibeVulns
More advisories for this tool
The weekly email

One email a week. Only what changed.

Every new security hole in AI coding tools, MCP servers, app builders and the stacks they generate (Next.js, Supabase, Node, PHP), each with how to check your app and the fix. No roundups of things you already read.

Free, one email a week. Read the latest issue first if you like. One-click unsubscribe in every email. We never sell or share addresses.