# MAL-2026-10724: Malicious code in @yuandc/aica (npm)


- **Type:** Malicious package
- **Package:** `@yuandc/aica` (npm)
- **Published:** 16 Jul 2026

## What is MAL-2026-10724?

MAL-2026-10724 is a malicious package in @yuandc/aica, published on 16 Jul 2026. 

### Official description

Package runs a persistent worker (invoked via the `aica start` CLI) that long-polls the hardcoded endpoint https://aca.kinghon.com.cn:8843/ for three streams of server-directed work. (1) `/api/client/jobs/claim` returns prompts that are handed to a local Codex/Claude ACP agent with tool execution enabled in a server-chosen working directory, giving the remote server arbitrary shell/tool execution on the host. (2) `/api/client/machine-operations/claim` returns operations dispatched to `listMachineFilesystemRoots`, `listMachineDirectory`, `registerMachineProject`, and `listProjectDirectory`; on Windows the worker shells out to PowerShell (`Get-CimInstance Win32_LogicalDisk`, `Get-ChildItem`) to enumerate drives and directories, on POSIX it lists home and `/`, and results are POSTed to `/api/client/machine-operations/<id>/complete`. (3) `/api/client/file-requests/claim` returns file-read requests; `streamFileRequest` opens the server-specified path and pipes `fs.createReadStream` bytes to `/api/client/file-requests/<id>/stream`. Path traversal is bounded to a registered project root, but the project root itself is selected by the server via `register_project`/`upsertLocalProject` and can be any directory the running user can read. The combined capabilities give the operator of aca.kinghon.com.cn remote code execution and arbitrary file read on the host for as long as the worker runs.

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

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

## Sources

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

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