Which versions of emittery-up are malicious?

The following npm versions of emittery-up are flagged malicious: 0.7.2, 0.8.2, 1.8.2. Treat any of these as compromised.

How do I remediate emittery-up if I installed it?

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

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

Yes — emittery-up is associated with the RLMA-2025-04509, RLUA-2025-05775 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 emittery-up across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for emittery-up (3 malicious versions).

Malicious package

emittery-upnpm

Advisory published Aug 28, 2025Updated Dec 2, 2025

emittery-up is a confirmed malicious npm package (MAL-2025-41554) that executes malicious code on install (malicious versions 0.7.2, 0.8.2, 1.8.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in emittery-up (npm)

MAL-2025-41554

Immediate action

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

npm uninstall emittery-up

Malicious versions

3 flagged

0.7.20.8.21.8.2

Indicators of compromise (SHA-256)

9c6b32fb8474a1f4f2aa3c294e5dbe29154b699711a109e51f7c933df21dfacf

1dd5b8c44beb200e98dc92abc8a82ad475b69b8e439225203e5f3e5e76c452d6

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-04509RLUA-2025-05775

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks emittery-up-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