Which versions of pkgnewfefame1 are malicious?

The following npm versions of pkgnewfefame1 are flagged malicious: 3.2.1. Treat any of these as compromised.

How do I remediate pkgnewfefame1 if I installed it?

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

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

Yes — pkgnewfefame1 is associated with the RLMA-2026-01493, RLUA-2026-02025 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 pkgnewfefame1 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pkgnewfefame1 (version 3.2.1).

Malicious package

pkgnewfefame1npm

Advisory published Mar 18, 2026Updated Apr 16, 2026

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

Malicious code in pkgnewfefame1 (npm)

MAL-2026-1816

Immediate action

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

npm uninstall pkgnewfefame1

What this malware does

The package pkgnewfefame1 was found to contain malicious code.

Malicious versions

1 flagged

3.2.1

Indicators of compromise (SHA-256)

5101b98ec1f550b43d291433172e441372a98f5d285afb7e156aed876c00aead

784cb2a0a3df5c95ee2f3f5b348780d29ffa4e6d03263d5611531f0b6babe20e

0f12e8b5223e452cce3d4c13dd04204507b4c5b8d445058c5fb32a67959cbe88

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01493RLUA-2026-02025

References

reversinglabs.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks pkgnewfefame1-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