# MAL-2026-14298: Malicious code in emoji-prints-fancy (npm)


- **Type:** Malicious package
- **Package:** `emoji-prints-fancy` (npm)
- **Published:** 19 Aug 2026
- **Also known as:** GHSA-m523-mggx-3fgr

## What is MAL-2026-14298?

MAL-2026-14298 is a malicious package in emoji-prints-fancy, published on 19 Aug 2026. 

### Official description

The package advertises itself as a colorized logger, but dist/index.js requires./logger, which at module load AES-256-CBC-decrypts a hardcoded ciphertext using a hardcoded passphrase, salt and IV (pbkdf2Sync with sha1, 100000 iterations) and passes the resulting plaintext to child_process.spawn with { shell: true, windowsHide: true, stdio: 'ignore' } via a _resolveConfig -> _runSystemTask path invoked by a top-level _warmConfigCache() call. Multiple decoy helpers (_checkResources, _registerToken, _semverCompare, _emitEvent, _poolBucket) surround the payload path and provide no functionality, and the AES layer serves only to conceal the executed command from static inspection. Any consumer that installs and require()s or imports this package silently executes the concealed shell command on the installer's host with output suppressed.

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

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-14298 is a malicious package: emoji-prints-fancy (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-14298/ (Markdown: https://insights.sbomify.com/MAL-2026-14298/index.md)
```

## Sources

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

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