Which versions of terminal-structured-logger are malicious?

The following npm versions of terminal-structured-logger are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate terminal-structured-logger if I installed it?

Remove terminal-structured-logger 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 terminal-structured-logger — how do I know if it already compromised me?

If terminal-structured-logger 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 terminal-structured-logger part of a known attack campaign?

Yes — terminal-structured-logger is associated with the GHSA-9ggp-5rq8-jmff, RLMA-2026-05333, RLUA-2026-05631 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 terminal-structured-logger 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 terminal-structured-logger (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging terminal-structured-logger across your stack and pipelines.

Malicious package

terminal-structured-loggernpm

terminal-structured-logger is a confirmed malicious npm package (MAL-2026-5867) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in terminal-structured-logger (npm)

MAL-2026-5867

Immediate action

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

npm uninstall terminal-structured-logger

What this malware does

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.

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

14080e4c54ea68f090ab98ee4eb27c7e987fe2d5e7ed6c5bb37ed89504a43099

32ed3bb9bcfeec3e85d091a4046347e1f0bf7f281048b777f1dadf47d93f1de9

b7d7ac64de13d84fe379a52b629a4d48323e5556565a8c3aa8243399d2dc4997

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 terminal-structured-logger (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging terminal-structured-logger across your stack and pipelines.
If you installed it — respond
Remove terminal-structured-logger 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 terminal-structured-logger 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 terminal-structured-logger 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. terminal-structured-logger on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9ggp-5rq8-jmffRLMA-2026-05333RLUA-2026-05631

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks terminal-structured-logger-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