custom-plugins-request-factorynpm
custom-plugins-request-factory is a confirmed malicious npm package (MAL-2026-12668) that executes malicious code on install (malicious version 35.5.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in custom-plugins-request-factory (npm)
What this malware does
The package's main entry auto-requires setup.js on load, which fetches a platform-specific executable from split-string-obfuscated Cloudflare Workers endpoints (oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev), writes it to /tmp or %TEMP% under a disguised name (.cache_<hex> or dotnet_diag_<hex>.exe), chmods it 0755 on POSIX, and spawns it detached via /bin/sh -c or cmd.exe. If HTTPS delivery fails, setup.js reassembles a base64-encoded payload from DNS TXT records under *.dl.wel1.ru (sdk./ext./pkg./net.dl.wel1.ru) as a covert-channel fallback, decodes it, writes it to disk, and executes it. Network destinations and the child_process require are assembled at runtime from split string fragments, and the package is framed as an analytics/telemetry SDK. lib/telemetry.js ships a parallel write-chmod-spawn dropper with the same obfuscation pattern. Requiring or installing the package results in execution of an opaque attacker-controlled binary on the host.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for custom-plugins-request-factory (version 35.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging custom-plugins-request-factory across your stack and pipelines.
If you installed it — respond
Remove custom-plugins-request-factory 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 custom-plugins-request-factory 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 custom-plugins-request-factory 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 custom-plugins-request-factory-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.