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

ms-affiliate-linksnpm

Malicious code in ms-affiliate-links (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2643
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ms-affiliate-links

What this malware does

The package ms-affiliate-links 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.

Malicious versions

1 flagged
99.0.0

Indicators of compromise (SHA-256)

ab4cc1e50ba42205438ad4545163f0b82122b7cc28ee037793e09f46f2b640a0
dcc81049c4459a62812c221192f3a89e23aa1e292eaf247c67b9f851bcb4837a
341048b16926b4d40796ca96aef3816934a2b84602c26451638154b6d90ab5d8

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 ms-affiliate-links (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 ms-affiliate-links across your stack and pipelines.

  2. If you installed it — respond

    Remove ms-affiliate-links 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 ms-affiliate-links 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 ms-affiliate-links 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. ms-affiliate-links 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-44p5-8q53-5vm5RLMA-2026-01994

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks ms-affiliate-links-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.

ms-affiliate-links (npm) malicious package — MAL-2026-2643 | O3 Security