Which versions of figlet-chalk-render are malicious?

The following npm versions of figlet-chalk-render are flagged malicious: 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 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 figlet-chalk-render part of a known attack campaign?

Yes — figlet-chalk-render is associated with the IN-MAL-2026-020607 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?

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

Malicious package

figlet-chalk-rendernpm

figlet-chalk-render is a confirmed malicious npm package (MAL-2026-17226) that executes malicious code on install (malicious version 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

The package is advertised as a chalk+figlet wrapper but index.js contains a top-level IIFE that runs on require. On Windows hosts, it reconstructs the module names 'https', 'os', 'fs', 'path', and 'child_process' and the method name 'spawn' from char-code arrays, hex escapes, and string concatenation to hide the network and execution chain. It then decodes the hardcoded plain-HTTP URL http://104.234.65.75:700/setup.exe and the filename RuntimeBroker.exe (masquerading as a legitimate Windows binary), downloads the payload into the OS temp directory via https.get piped to createWriteStream, and spawns it detached with windowsHide: true and.unref(). Execution is gated to skip environments where CI, SANDBOX, GITHUB_ACTIONS, or TRAVIS are set, evading sandbox and CI analysis. The obfuscation, bare-IP plain-HTTP delivery, RuntimeBroker.exe masquerade, and CI-evasion gate are inconsistent with the package's stated purpose and match an install/require-time Windows dropper.

Malicious versions

1 flagged

1.2.1

Indicators of compromise (SHA-256)

992cf49b88be09149971d4ac18fe2a4b61d242186f553cb3283a26970b886d7f

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for figlet-chalk-render (version 1.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging figlet-chalk-render across your stack and pipelines.
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 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 figlet-chalk-render 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. figlet-chalk-render on npm has been identified as a malicious package (version 1.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020607

References

npmjs.com

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