Which versions of my-not-little-durgham are malicious?

The following npm versions of my-not-little-durgham are flagged malicious: 8.99.99. Treat any of these as compromised.

How do I remediate my-not-little-durgham if I installed it?

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

If my-not-little-durgham 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-not-little-durgham part of a known attack campaign?

Yes — my-not-little-durgham is associated with the RLMA-2026-01791 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-not-little-durgham across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for my-not-little-durgham (version 8.99.99).

Malicious package

my-not-little-durghamnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

my-not-little-durgham is a confirmed malicious npm package (MAL-2026-2374) that executes malicious code on install (malicious version 8.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in my-not-little-durgham (npm)

MAL-2026-2374

Immediate action

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

npm uninstall my-not-little-durgham

What this malware does

The package my-not-little-durgham was found to contain malicious code.

Malicious versions

1 flagged

8.99.99

Indicators of compromise (SHA-256)

728b36185ef3691f80fc3de98b8706616e84460e287ec507d471e9c691fd5f6f

c931edc7578c330e6d7b1b0dac74c52ea1583e1ac075ee03949b2a2d197b4adb

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01791

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks my-not-little-durgham-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