Which versions of multer-orm are malicious?

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

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

multer-orm establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed multer-orm — how do I know if it already compromised me?

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

Yes — multer-orm is associated with the IN-MAL-2026-009288 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 multer-orm 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 multer-orm (version 2.0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging multer-orm across your stack and pipelines.

Malicious package

multer-ormnpm

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

MAL-2026-10064

Immediate action

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

npm uninstall multer-orm

What this malware does

Package name impersonates the popular multer middleware and copies its README/repo metadata. On require('multer-orm'), index.js loads lib/feature.js, which at module load fetches a JSON document from https://hilbert-self.vercel.app/, extracts a downloader_url field, downloads an opaque binary over http/https with no pinning or integrity check, writes it as chrome.exe under the Chrome User Data directory to masquerade as the browser, and executes it via execFile/spawn (chmod 755 on non-Windows). When running as administrator on Windows, the code first writes and runs a PowerShell script that calls Add-MpPreference -ExclusionPath on the staging directory to evade Windows Defender; when not elevated, it re-spawns itself via powershell -Command Start-Process... -Verb RunAs -WindowStyle Hidden to obtain UAC elevation. The dropper logic in lib/feature.js is hidden behind obfuscator.io-style string-array rotation that conceals identifiers such as child_process, powershell, chrome.exe, Add-MpPreference, and the C2 hostname. There is no legitimate multipart/form-data middleware functionality — the package exists solely to deliver the remote payload to anyone who mistypes multer.

Malicious versions

1 flagged

2.0.6

Indicators of compromise (SHA-256)

489805f0242c070653fa4e09c782d8135971a370b3ae292d31d721507332a12f

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for multer-orm (version 2.0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging multer-orm across your stack and pipelines.
If you installed it — respond
multer-orm establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If multer-orm 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 multer-orm 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. multer-orm on npm has been identified as a malicious package (version 2.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009288

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks multer-orm-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring