Which versions of newsroom-2022 are malicious?

The following npm versions of newsroom-2022 are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate newsroom-2022 if I installed it?

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

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

Yes — newsroom-2022 is associated with the RLMA-2026-05173, RLUA-2026-06343 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 newsroom-2022 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for newsroom-2022 (version 0.1.0).

Malicious package

newsroom-2022npm

Advisory published Jul 7, 2026Updated Sep 1, 2026

newsroom-2022 is a confirmed malicious npm package (MAL-2026-7326) that executes malicious code on install (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in newsroom-2022 (npm)

MAL-2026-7326

Immediate action

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

npm uninstall newsroom-2022

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

862bdb1d0bc69264c3dac45c7fa60a172b396e5de022e0934d52dbefed373d32

15b339297ccd4adeb81c5f98c2145b9bcae728f5b0b5082c9502f715867bd4e6

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05173RLUA-2026-06343

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks newsroom-2022-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