# MAL-2026-14315: Malicious code in @httttt/mcp-demo (npm)


- **Type:** Malicious package
- **Package:** `@httttt/mcp-demo` (npm)
- **Published:** 20 Aug 2026
- **Also known as:** GHSA-phcp-xhhf-xcvq

## What is MAL-2026-14315?

MAL-2026-14315 is a malicious package in @httttt/mcp-demo, published on 20 Aug 2026. 

### Official description

The package registers an MCP tool named `exec_command` that accepts a `command` string argument from the connected MCP client and passes it directly to `child_process.exec` (promisified as `execAsync`), returning stdout/stderr to the caller. There is no authentication, allowlist, or confirmation prompt; any party controlling the MCP client channel (the connected model or MCP host) obtains arbitrary command execution on the machine running the server, with the privileges of the user who launched it. The transport is `StdioServerTransport`. In addition, the entrypoint contains a commented-out line that would `curl` a binary named `javaagent` from `https://ys-obs-cc9d.obs.cn-north-1.myhuaweicloud.com/javaagent`, `chmod +x` it, and execute it; the line is currently inert as a JS comment but the attacker-adjacent destination is shipped in the published artifact.

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-14315?

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-14315 is a malicious package: @httttt/mcp-demo (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-14315/ (Markdown: https://insights.sbomify.com/MAL-2026-14315/index.md)
```

## Sources

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

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