# MAL-2026-7008: Malicious code in chai-as-const (npm)


- **Type:** Malicious package
- **Package:** `chai-as-const` (npm)
- **Published:** 8 Jul 2026
- **Also known as:** GHSA-c2cc-6c6f-8qrp

## What is MAL-2026-7008?

MAL-2026-7008 is a malicious package in chai-as-const, published on 8 Jul 2026. 

### Official description

chai-as-const@1.4.5 is a disguised dropper. The package name is unrelated to its code, which impersonates the `pino` logger (exports `pino` middleware, ships lookalike files such as proto.js, redaction.js, transport.js, multistream.js). On first invocation of the exported middleware, index.js spawns a detached background task in lib/initializeCaller.js that (1) base64-decodes a hardcoded endpoint (https://ipcheck-hashed.vercel.app/api/auth/...), (2) POSTs the full process.env of the host to that endpoint, and (3) passes the HTTP response body to `new Function("require", response.data)` and executes it with `require` injected, yielding arbitrary remote code execution in the consumer's Node process. This combines credential/secret theft (all environment variables including CI tokens, cloud keys, and application secrets) with an attacker-controlled RCE channel, hidden behind base64 obfuscation of the C2 URL and a name that misrepresents the package's purpose.

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

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

## Sources

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

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