Which versions of emoji-prints-fancy are malicious?

The following npm versions of emoji-prints-fancy are flagged malicious: 5.6.4. Treat any of these as compromised.

How do I remediate emoji-prints-fancy if I installed it?

emoji-prints-fancy is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed emoji-prints-fancy — how do I know if it already compromised me?

If emoji-prints-fancy was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is emoji-prints-fancy part of a known attack campaign?

Yes — emoji-prints-fancy is associated with the IN-MAL-2026-018419 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find emoji-prints-fancy across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for emoji-prints-fancy (version 5.6.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging emoji-prints-fancy across your stack and pipelines.

Malicious package

emoji-prints-fancynpm

emoji-prints-fancy is a confirmed malicious npm package (MAL-2026-14298) that steals credentials and exfiltrates sensitive data (malicious version 5.6.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in emoji-prints-fancy (npm)

MAL-2026-14298

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall emoji-prints-fancy

What this malware does

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.

Malicious versions

1 flagged

5.6.4

Indicators of compromise (SHA-256)

163576a0a8b626c88261c8cc54c5049d981015c80145ad36e2710fff5014afbe

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for emoji-prints-fancy (version 5.6.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging emoji-prints-fancy across your stack and pipelines.
If you installed it — respond
emoji-prints-fancy is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If emoji-prints-fancy was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks emoji-prints-fancy before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. emoji-prints-fancy on npm has been identified as a malicious package (version 5.6.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018419

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks emoji-prints-fancy-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database