Which versions of resethp are malicious?

The following npm versions of resethp are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate resethp if I installed it?

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

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

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

Search your lockfiles and build artifacts for resethp (2 malicious versions).

Malicious package

resethpnpm

Advisory published Dec 23, 2025Updated Jan 2, 2026

resethp is a confirmed malicious npm package (MAL-2025-192858) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in resethp (npm)

MAL-2025-192858

Immediate action

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

npm uninstall resethp

What this malware does

The package resethp was found to contain malicious code.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

2b62e0a932e73bea4932fb04eab3ca2f3cc35234444c040fdc46ec8d5acba660

97111004c64266b40270ee122953b5fbccceb2b059cebb1d69b9892a4a55ff9d

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06464

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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