Which versions of no-function-declare-after-return are malicious?

The following npm versions of no-function-declare-after-return are flagged malicious: 5.1.0. Treat any of these as compromised.

How do I remediate no-function-declare-after-return if I installed it?

Remove no-function-declare-after-return 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 no-function-declare-after-return — how do I know if it already compromised me?

If no-function-declare-after-return 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 no-function-declare-after-return part of a known attack campaign?

Yes — no-function-declare-after-return is associated with the RLMA-2026-01795 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 no-function-declare-after-return across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for no-function-declare-after-return (version 5.1.0).

Malicious package

no-function-declare-after-returnnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

no-function-declare-after-return is a confirmed malicious npm package (MAL-2026-2377) that executes malicious code on install (malicious version 5.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in no-function-declare-after-return (npm)

MAL-2026-2377

Immediate action

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

npm uninstall no-function-declare-after-return

What this malware does

The package no-function-declare-after-return was found to contain malicious code.

Malicious versions

1 flagged

5.1.0

Indicators of compromise (SHA-256)

1765f8d2f3a39520b1372749ce87a89bd4b9cfbb244acaebb1d7d1b4dee61f82

40f5de9e9b3e66259de31f34cf47ef3b38b8fefc1e80d860c6dab7cade495bca

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01795

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks no-function-declare-after-return-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