Which versions of figlet-chalk-render are malicious?

The following npm versions of figlet-chalk-render are flagged malicious: 1.0.0, 1.2.1. Treat any of these as compromised.

How do I remediate figlet-chalk-render if I installed it?

Remove figlet-chalk-render from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed figlet-chalk-render — how do I know if it already compromised me?

If figlet-chalk-render was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is figlet-chalk-render part of a known attack campaign?

Yes — figlet-chalk-render is associated with the IN-MAL-2026-020607, IN-MAL-2026-020818 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 figlet-chalk-render across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for figlet-chalk-render (2 malicious versions).

Malicious package

figlet-chalk-rendernpm

Advisory published Sep 28, 2026Updated Sep 30, 2026

figlet-chalk-render is a confirmed malicious npm package (MAL-2026-17226) that executes malicious code on install (malicious versions 1.0.0, 1.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in figlet-chalk-render (npm)

MAL-2026-17226

Immediate action

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

npm uninstall figlet-chalk-render

What this malware does

On every require('figlet-chalk-render'), a top-level IIFE queries https://registry.npmjs.org/figlet-chalk-render/latest and, if a newer version exists, spawns npm install figlet-chalk-render@<latest> with cwd set to path.join(__dirname, '..', '..') (the consumer project's root) and stdio ignored. The https, child_process, and path core-module names are loaded via hex-escaped string literals ('\x63\x68\x69\x6c\x64\x5f\x70\x72\x6f\x63\x65\x73\x73', etc.) rather than plain identifiers, deliberately hiding the sensitive requires backing the auto-update. The behavior is undocumented in the README. Every consumer that imports the module receives whatever the latest published version happens to be at that moment, executed with the installer's npm privileges and lifecycle scripts, giving anyone who later controls this package name a silent code-execution channel into every installer's project tree. The hex-obfuscation of the module names is anti-evasion and rebuts a benign-self-update reading: legitimate insecure-update code does not disguise require('child_process').

Malicious versions

2 flagged

1.0.01.2.1

Indicators of compromise (SHA-256)

992cf49b88be09149971d4ac18fe2a4b61d242186f553cb3283a26970b886d7f

d5ccd0a988525d8128b520a46c4271e26ae5fe2f99accf28f37d4c7370b66de4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for figlet-chalk-render (2 malicious versions).
If you installed it — respond
Remove figlet-chalk-render from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If figlet-chalk-render was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. figlet-chalk-render on npm has been identified as a malicious package (versions 1.0.0, 1.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020607IN-MAL-2026-020818

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks figlet-chalk-render-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database