# MAL-2026-10056: Malicious code in chain-chai-await (npm)


- **Type:** Malicious package
- **Package:** `chain-chai-await` (npm)
- **Published:** 9 Jul 2026
- **Also known as:** GHSA-v7w8-4wfr-cvwf

## What is MAL-2026-10056?

MAL-2026-10056 is a malicious package in chain-chai-await, published on 9 Jul 2026. 

### Official description

The package presents itself as a pino-compatible logger (exports `pino`, mirrors pino's lib/ layout with proto.js/redaction.js/transport.js/multistream.js/levels.js/time.js/symbols.js, and copies pino's defaultOptions shape) but has no relationship to the real pino package. When a consumer requires the package and invokes the exported middleware factory, index.js spawns lib/caller.js as a detached Node subprocess. caller.js performs an axios GET to https://jsonkeeper.com/b/K80JD, reads the `cookie` field from the JSON response, and executes it via `new Function.constructor("require", s)(require)` — arbitrary remote code execution in the consumer's Node process with full access to `require`. The fetch is retried up to 5 times. lib/const.js additionally stores a base64-encoded backup endpoint (aHR0cHM6Ly9qc29ua2VlcGVyLmNvbS9iL1pLNDVK → https://jsonkeeper.com/b/ZK45J) and base64-encoded header key/value (`x-secret-key`, `_`) used by the loader. The pino cover story, mirrored file layout, obfuscated backup URL, and remote-fetch-and-execute primitive against a public paste-like host are the fingerprint of a dropper disguised as a logging library.

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

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-10056 is a malicious package: chain-chai-await (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-10056/ (Markdown: https://insights.sbomify.com/MAL-2026-10056/index.md)
```

## Sources

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

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