Which versions of advertising-events are malicious?

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

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

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

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

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

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

Malicious package

advertising-eventsnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

advertising-events is a confirmed malicious npm package (MAL-2026-1648) 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-events (npm)

MAL-2026-1648

Immediate action

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

npm uninstall advertising-events

What this malware does

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

Malicious versions

3 flagged

99.0.099.0.199.0.2

Indicators of compromise (SHA-256)

5c4297a6cc895ef3cca638c50fe335db0ef2b0ff88535305fe1ebe9d39d9ed21

f9e784ce1a0573b476f4232dcdc6136efaa217d3483765875dbea0aae015542d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for advertising-events (3 malicious versions).
If you installed it — respond
Remove advertising-events 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-events 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-events 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-01096

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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