Which versions of @bingads-webui-cc-react/edit-primary-contact are malicious?

The following npm versions of @bingads-webui-cc-react/edit-primary-contact are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate @bingads-webui-cc-react/edit-primary-contact if I installed it?

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.

I already installed @bingads-webui-cc-react/edit-primary-contact — how do I know if it already compromised me?

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

Is @bingads-webui-cc-react/edit-primary-contact part of a known attack campaign?

Yes — @bingads-webui-cc-react/edit-primary-contact is associated with the RLMA-2026-00968 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 @bingads-webui-cc-react/edit-primary-contact across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @bingads-webui-cc-react/edit-primary-contact (version 99.9.9).

Malicious package

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

Advisory published Mar 18, 2026Updated Mar 23, 2026

@bingads-webui-cc-react/edit-primary-contact is a confirmed malicious npm package (MAL-2026-1587) 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 @bingads-webui-cc-react/edit-primary-contact (npm)

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

Find it
Search your lockfiles and build artifacts for @bingads-webui-cc-react/edit-primary-contact (version 99.9.9).
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.
Did it already run?
If @bingads-webui-cc-react/edit-primary-contact 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. @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

Explore

All malware advisories How O3 detects malware Vulnerability database