Which versions of partner-tracker are malicious?

The following npm versions of partner-tracker are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate partner-tracker if I installed it?

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

If partner-tracker 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 partner-tracker part of a known attack campaign?

Yes — partner-tracker is associated with the GHSA-49v3-3255-4m4h 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 partner-tracker 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 partner-tracker (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging partner-tracker across your stack and pipelines.

Malicious package

partner-trackernpm

Malicious code in partner-tracker (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2426

Immediate action

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

npm uninstall partner-tracker

What this malware does

The package partner-tracker 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 'partner-tracker' @ 99.0.0 (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

1 flagged

99.0.0

Indicators of compromise (SHA-256)

b2f8513bc3ec574126bfafd51edcbaeb34a4ed9bd266303ccb5398652fdd026a

cf0b992863c06f797a9dddef6a493b0391094c9a2ae31fec47e961dd1afdf562

cfd28d767cd7e0db43c5c52d0b219663552acd6a5f60a34795736624c5cb6129

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

Campaign

GHSA-49v3-3255-4m4h

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks partner-tracker-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