Which versions of node-multer are malicious?

The following npm versions of node-multer are flagged malicious: 3.5.7. Treat any of these as compromised.

How do I remediate node-multer if I installed it?

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

If node-multer 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 node-multer part of a known attack campaign?

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

Search your lockfiles and build artifacts for node-multer (version 3.5.7).

Malicious package

node-multernpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

node-multer is a confirmed malicious npm package (MAL-2026-2378) that executes malicious code on install (malicious version 3.5.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-multer (npm)

MAL-2026-2378

Immediate action

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

npm uninstall node-multer

What this malware does

The package node-multer was found to contain malicious code.

Malicious versions

1 flagged

3.5.7

Indicators of compromise (SHA-256)

ac071000b6c869ddf4dffecfb76b05cbab824a6ca662eacf05f6b0ad492616bc

6fd13a20e1e6edfd702b510f8205a60c9826a214ac27b04e1c6b48dee5f74d76

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01797

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks node-multer-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