Which versions of @cheqplease/structured-logger are malicious?

The following npm versions of @cheqplease/structured-logger are flagged malicious: 2.2.3, 2.2.5, 2.2.15, 9.1.15, 9.3.2. Treat any of these as compromised.

How do I remediate @cheqplease/structured-logger if I installed it?

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

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

Yes — @cheqplease/structured-logger is associated with the GHSA-x55c-jcjf-hj69 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 @cheqplease/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 @cheqplease/structured-logger (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @cheqplease/structured-logger across your stack and pipelines.

Malicious package

@cheqplease/structured-loggernpm

Malicious code in @cheqplease/structured-logger (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192434

Immediate action

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

npm uninstall @cheqplease/structured-logger

What this malware does

The package @cheqplease/structured-logger was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified '@cheqplease/structured-logger' @ 9.1.15 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

5 flagged

2.2.32.2.52.2.159.1.159.3.2

Indicators of compromise (SHA-256)

c7b2eaf9855d341e5f9ab565ebc877ff7ff45cbefa1f8c14282df13a42104e49

9739b1daa670ddf73fd79ce8ca9abde7ae2824f7d12d1c85ada0af050a0cd94c

20d22361ee41fd7a8906f4a1014f00da72310b824c28cc1b0d23868cfef321cb

7f4111b892bba0089b3619c99cd5135fa3693d4a78c790a23017e359beff0cd8

ba19fbf2e13483ed528a6f41300aa9442b218462ddc993cf8766151bc2ac7dc9

c6ef1fa05f2ae34a0acbddf00e8be9c566e82f3398f990ca95eeceb8dec8e82d

6541f5143f0a03f4093360a265b5a10245460f1b0608d2e37ce0fd7e67018ca4

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

Campaign

GHSA-x55c-jcjf-hj69

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @cheqplease/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