Which versions of partnerss are malicious?

The following npm versions of partnerss are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate partnerss if I installed it?

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

If partnerss was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find partnerss across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for partnerss (version 99.9.9).

Malicious package

partnerssnpm

Advisory published Feb 4, 2026Updated Feb 6, 2026

partnerss is a confirmed malicious npm package (MAL-2026-717) that executes malicious code on install (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in partnerss (npm)

MAL-2026-717

Immediate action

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

npm uninstall partnerss

What this malware does

The package partnerss was found to contain malicious code.

The OpenSSF Package Analysis project identified 'partnerss' @ 99.9.9 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

8760f774e513cf8d18beaa321298ecd8c1a0eb17031f919b106c5c8bf45eeb41

c370b0dbfdf4006f77ab698296da5eef2bb1a5ca43e91b932711518a3a0b8c5c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for partnerss (version 99.9.9).
If you installed it — respond
Remove partnerss 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 partnerss was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. partnerss on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks partnerss-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