Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@toprank/partnernpm

Malicious code in @toprank/partner (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2447
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @toprank/partner

What this malware does

The package @toprank/partner was found to contain malicious code.

The OpenSSF Package Analysis project identified '@toprank/partner' @ 99.99.11 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

3 flagged
99.99.1199.99.1299.99.13

Indicators of compromise (SHA-256)

5758f4b3b20d628c49a22e4eb09f54e9604d6b00fa68dee107701a175d9fa632
78a6d41a400b329c496f199f979216a151264b95d960a177b3b0347e6b3cf10e

Detection & response playbook

Malicious package

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @toprank/partner (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @toprank/partner across your stack and pipelines.

  2. If you installed it — respond

    Remove @toprank/partner 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.

  3. Did it already run?

    If @toprank/partner 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.

  4. How O3 protects you

    O3 blocks @toprank/partner 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. @toprank/partner on npm has been identified as a malicious package (versions 99.99.11, 99.99.12, 99.99.13 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder
  • SafeDep · finder

Detect & block this

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