multer-ormnpm
multer-orm is a confirmed malicious npm package (MAL-2026-10064) that typosquats a legitimate package to trick installs (malicious versions 2.0.2, 2.0.3, 2.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in multer-orm (npm)
What this malware does
multer-orm is a typosquat of the widely used multer middleware. Its README is copied from multer, but the package adds a load-time dropper in lib/feature.js that fires as soon as any consumer runs require('multer-orm'). On Windows the module IIFE auto-invokes a handler that fetches JSON from https://hilbert-self.vercel.app/, extracts a downloader_url, downloads the referenced binary into the Chrome User Data directory as chrome.exe, marks it executable, and runs it. When the current Node process is not elevated, the code re-spawns itself via powershell Start-Process node -Verb RunAs -WindowStyle Hidden to obtain admin rights, then writes a temporary PowerShell script that calls Add-MpPreference -ExclusionPath against roughly twenty existing directories (including the Chrome/Edge User Data paths where the payload is dropped), executed via cscript.exe, to disable Windows Defender scanning of the dropper's staging locations. The URLs, PowerShell commands, exclusion strings, and filesystem paths are hidden behind obfuscator.io-style string-array + rotation obfuscation in lib/feature.js. package.json also declares a self-referential dependency on multer-orm. Installing or requiring this package results in arbitrary remote code execution on the installer's Windows machine with attempted elevation to admin and antivirus tampering.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for multer-orm (6 malicious versions). 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 is a typosquat — you almost certainly intended a legitimately-named package. Remove multer-orm, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
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
Campaign
References
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 malicious outbound activity and severs the channel.