Which versions of identity-emitter are malicious?

The following npm versions of identity-emitter are flagged malicious: 0.1.5, 0.1.7, 0.1.8, 1.0.0, 1.0.5. Treat any of these as compromised.

How do I remediate identity-emitter if I installed it?

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

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

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

Search your lockfiles and build artifacts for identity-emitter (5 malicious versions).

Malicious package

identity-emitternpm

Advisory published Jan 2, 2026Updated Mar 19, 2026

identity-emitter is a confirmed malicious npm package (MAL-2026-17) that executes malicious code on install (malicious versions 0.1.5, 0.1.7, 0.1.8…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in identity-emitter (npm)

MAL-2026-17

Immediate action

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

npm uninstall identity-emitter

What this malware does

The package identity-emitter was found to contain malicious code.

Malicious versions

5 flagged

0.1.50.1.70.1.81.0.01.0.5

Indicators of compromise (SHA-256)

b2e21ae9a5babde61e78ed9c713ec2e845a44ac55b19fb0d9cd48561159bb16a

0537a2cdefbd766a9d0e6c0426fbcd99ee58724dd49ab0010a43c56a1ab97a1b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for identity-emitter (5 malicious versions).
If you installed it — respond
Remove identity-emitter 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 identity-emitter 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. identity-emitter on npm has been identified as a malicious package (versions 0.1.5, 0.1.7, 0.1.8, 1.0.0, 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01351

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks identity-emitter-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