# MAL-2026-6222: Malicious code in create-mono-package (npm)


- **Type:** Malicious package
- **Package:** `create-mono-package` (npm)
- **Published:** 19 Jun 2026

## What is MAL-2026-6222?

MAL-2026-6222 is a malicious package in create-mono-package, published on 19 Jun 2026. 

### Official description

The package's postinstall hook (.prepare.cjs) collects host fingerprint data (os.hostname(), os.userInfo().username, platform/arch, all non-internal network interface IPs, npm registry) plus a full dump of process.env (only keys prefixed with `npm_lifecycle` are filtered out) and HTTPS-POSTs the JSON payload to open.larksuite.com. Both the destination host and URL path are obfuscated: the hostname is built from a reversed charcode array with a -7 offset (`_hostDecoder`), and the path is XOR-decoded against key `Zk9x` (`_pathDecoder`). The send is wrapped in extensive sandbox/honeypot evasion — the script silently `process.exit(0)`s when env keys match analysis-pipeline prefixes (SANDYCLAW_, OPENCLAW_, PERMISO_, CHAINRADAR_, PYPI_POISON_, ASPECT_TLOG, THREAT_ANALYZER_MODEL) or when hostname/username matches patterns like detonat/cuckoo/virus/scan, and dummy values for GITHUB_TOKEN/NPM_TOKEN/AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY are explicitly skipped to avoid honeypots. On a real developer or CI machine, `npm install create-mono-package` ships every credential present in the environment (GitHub PATs, npm publish tokens, AWS keys, CI secrets, DB URIs) to the attacker-controlled Lark endpoint.

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

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-6222 is a malicious package: create-mono-package (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-6222/ (Markdown: https://insights.sbomify.com/MAL-2026-6222/index.md)
```

## Sources

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

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