Which versions of auth-1s7epg are malicious?

The following npm versions of auth-1s7epg are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate auth-1s7epg if I installed it?

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

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

Yes — auth-1s7epg is associated with the RLMA-2025-05689 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 auth-1s7epg across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for auth-1s7epg (version 1.0.0).

Malicious package

auth-1s7epgnpm

Advisory published Dec 1, 2025Updated Dec 2, 2025

auth-1s7epg is a confirmed malicious npm package (MAL-2025-191565) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in auth-1s7epg (npm)

MAL-2025-191565

Immediate action

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

npm uninstall auth-1s7epg

What this malware does

The package auth-1s7epg was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e805d6893d8b0909784731e8ebcea4387b65cab091c35398db730adf9090339f

f86979a79a49db20dee0fecc4bf5e9a531adf3c2134b68b0828ed143f12514b2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05689

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks auth-1s7epg-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