Which versions of advertising-shared are malicious?

The following npm versions of advertising-shared are flagged malicious: 99.0.0, 99.0.1, 99.0.2. Treat any of these as compromised.

How do I remediate advertising-shared if I installed it?

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

If advertising-shared 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 advertising-shared part of a known attack campaign?

Yes — advertising-shared is associated with the RLMA-2026-01098 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 advertising-shared across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for advertising-shared (3 malicious versions).

Malicious package

advertising-sharednpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

advertising-shared is a confirmed malicious npm package (MAL-2026-1650) that executes malicious code on install (malicious versions 99.0.0, 99.0.1, 99.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in advertising-shared (npm)

MAL-2026-1650

Immediate action

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

npm uninstall advertising-shared

What this malware does

The package advertising-shared was found to contain malicious code.

Malicious versions

3 flagged

99.0.099.0.199.0.2

Indicators of compromise (SHA-256)

77277973acdba409e40cf72546df7e83d69d66dde0fbb80918f6f17d3571ba19

f72c8f6eb16d0fa51374dcf78f95b3a6c9ac1ffcf8c72a0995c6425df9f83182

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for advertising-shared (3 malicious versions).
If you installed it — respond
Remove advertising-shared 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 advertising-shared 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. advertising-shared on npm has been identified as a malicious package (versions 99.0.0, 99.0.1, 99.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01098

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks advertising-shared-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