Which versions of cktool.config are malicious?

The following npm versions of cktool.config are flagged malicious: 1000.0.1. Treat any of these as compromised.

How do I remediate cktool.config if I installed it?

Remove cktool.config 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 cktool.config — how do I know if it already compromised me?

If cktool.config 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 cktool.config part of a known attack campaign?

Yes — cktool.config is associated with the GHSA-2rgm-r9mf-qcvf 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 cktool.config 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 cktool.config (version 1000.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cktool.config across your stack and pipelines.

Malicious package

cktool.confignpm

Malicious code in cktool.config (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2923

Immediate action

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

npm uninstall cktool.config

What this malware does

The package cktool.config 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 'cktool.config' @ 1000.0.1 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1000.0.1

Indicators of compromise (SHA-256)

c92df5aca7387071d8103ac7b4e49ef8ccfccfb565d02ec339c75759a62d50e6

7ab5059fb326d298c03d52ca07411ad4f38ed446293bd6206c87b11b6c78aa13

d17768ef72268e4f3e826458378ed35d149b66eee4e8ba9011ac3a56703d34a4

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

Campaign

GHSA-2rgm-r9mf-qcvf

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks cktool.config-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