Which versions of ehance-assistant33 are malicious?

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

How do I remediate ehance-assistant33 if I installed it?

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

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

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

Search your lockfiles and build artifacts for ehance-assistant33 (2 malicious versions).

Malicious package

ehance-assistant33npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

ehance-assistant33 is a confirmed malicious npm package (MAL-2026-1722) 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 ehance-assistant33 (npm)

MAL-2026-1722

Immediate action

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

npm uninstall ehance-assistant33

What this malware does

The package ehance-assistant33 was found to contain malicious code.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

0484eba4ddea99b9781108ed10f691227ceb3322bbb2c14ee90db72d151ca4a1

e90c1f0a123aa9318f8122bc029cc80bb41a66686963a0b51cd2047c79cb2f29

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ehance-assistant33 (2 malicious versions).
If you installed it — respond
Remove ehance-assistant33 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 ehance-assistant33 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. ehance-assistant33 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-2026-01272

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ehance-assistant33-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