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

@bingads-webui-cc-react/edit-primary-contactnpm

Malicious code in @bingads-webui-cc-react/edit-primary-contact (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1587
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @bingads-webui-cc-react/edit-primary-contact

What this malware does

The package @bingads-webui-cc-react/edit-primary-contact was found to contain malicious code.

Malicious versions

1 flagged
99.9.9

Indicators of compromise (SHA-256)

fbac40c4829c02c71e225319cdce9ff513aca78fb59df4258ffcb0ff5e6a5aed
d8db2de62135603996e4dfafbfd49878df32f1d35291bd473c636cef7b7303f6

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 @bingads-webui-cc-react/edit-primary-contact (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @bingads-webui-cc-react/edit-primary-contact across your stack and pipelines.

  2. If you installed it — respond

    Remove @bingads-webui-cc-react/edit-primary-contact 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 @bingads-webui-cc-react/edit-primary-contact 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 @bingads-webui-cc-react/edit-primary-contact 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. @bingads-webui-cc-react/edit-primary-contact 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.

Campaign

RLMA-2026-00968

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @bingads-webui-cc-react/edit-primary-contact-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