Which versions of example-nestjs-api are malicious?

The following npm versions of example-nestjs-api are flagged malicious: 10.0.1, 99.9.9. Treat any of these as compromised.

How do I remediate example-nestjs-api if I installed it?

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

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

Yes — example-nestjs-api is associated with the RLMA-2025-05008, RLUA-2026-05079, RLUA-2026-06227 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 example-nestjs-api across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for example-nestjs-api (2 malicious versions).

Malicious package

example-nestjs-apinpm

Advisory published Sep 26, 2025Updated Sep 1, 2026

example-nestjs-api is a confirmed malicious npm package (MAL-2025-47666) that executes malicious code on install (malicious versions 10.0.1, 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in example-nestjs-api (npm)

MAL-2025-47666

Immediate action

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

npm uninstall example-nestjs-api

Malicious versions

2 flagged

10.0.199.9.9

Indicators of compromise (SHA-256)

ad5a93f3b6db10e379ee7eccc8447299ad1cb1f35978de1393600b5d14ddfc39

71e4bc58679cc0d4ae3e153ee3ef51ac3d666afe1bf11e672672f5219397c1b5

50ff37300d6fce95cbad51acd609c8670830a32f2623f09761cb7c4d35337e8c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05008RLUA-2026-05079RLUA-2026-06227

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks example-nestjs-api-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