Which versions of nest-moralis are malicious?

The following npm versions of nest-moralis are flagged malicious: 2.27.4, 2.27.6, 2.27.7, 2.27.8. Treat any of these as compromised.

How do I remediate nest-moralis if I installed it?

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

If nest-moralis was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is nest-moralis part of a known attack campaign?

Yes — nest-moralis is associated with the GHSA-c29x-5m4q-2c7c 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 nest-moralis across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nest-moralis (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nest-moralis across your stack and pipelines.

Malicious package

nest-moralisnpm

Malicious code in nest-moralis (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1445

Immediate action

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

npm uninstall nest-moralis

What this malware does

The package nest-moralis was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

4 flagged

2.27.42.27.62.27.72.27.8

Indicators of compromise (SHA-256)

f5ebd5810f65b46e709e5d8a09a1b3a421a0aac599af1ef51e8bb433afddba48

7568b91354492a39b40ca156221b4a94c94808517fbf09ae48954ba5da0febfd

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nest-moralis (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nest-moralis across your stack and pipelines.
If you installed it — respond
Remove nest-moralis 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 nest-moralis was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks nest-moralis before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. nest-moralis on npm has been identified as a malicious package (versions 2.27.4, 2.27.6, 2.27.7, 2.27.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-c29x-5m4q-2c7c

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nest-moralis-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