Which versions of pt-sc-logger are malicious?

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

How do I remediate pt-sc-logger if I installed it?

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

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

Yes — pt-sc-logger is associated with the GHSA-c9cq-89w9-78h3 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 pt-sc-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 pt-sc-logger (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pt-sc-logger across your stack and pipelines.

Malicious package

pt-sc-loggernpm

Malicious code in pt-sc-logger (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2568

Immediate action

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

npm uninstall pt-sc-logger

What this malware does

The package pt-sc-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 'pt-sc-logger' @ 1.0.1 (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

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

a5656da2c926bda216f3cf685f592a25f130e6d542b81034d41f288b3b69fb21

e6c2c1507ade7736400cbd5ec29a90a838b07c2c690e01279a1845e5d5afb3af

deaf63bd8a081fcc49f46fdb9b4300abef500b33eba7034bbd8de142a60db3cd

925a5c001d049ecefbe72bc5ba4090904c882bf13b6f97493387fe3ed04a661f

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

Campaign

GHSA-c9cq-89w9-78h3

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks pt-sc-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