Which versions of my-benefits-web are malicious?

The following npm versions of my-benefits-web are flagged malicious: 1.0.0, 1.0.5, 1.0.6. Treat any of these as compromised.

How do I remediate my-benefits-web if I installed it?

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

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

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

Search your lockfiles and build artifacts for my-benefits-web (3 malicious versions).

Malicious package

my-benefits-webnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

my-benefits-web is a confirmed malicious npm package (MAL-2026-1794) that executes malicious code on install (malicious versions 1.0.0, 1.0.5, 1.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in my-benefits-web (npm)

MAL-2026-1794

Immediate action

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

npm uninstall my-benefits-web

What this malware does

The package my-benefits-web was found to contain malicious code.

Malicious versions

3 flagged

1.0.01.0.51.0.6

Indicators of compromise (SHA-256)

161fcab0efcf2df56e4d1f08230d6fe76d6bff7f60b8bc8c3ad78cfa976baf82

c5aaf8254cd355ca47587aa46a9489d933410356052f3a2c2596404e70de7912

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01437

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks my-benefits-web-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