What does the custom-plugins-request-factory malware do?

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_ or dotnet_diag_ .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 requi

Which versions of custom-plugins-request-factory are malicious?

The following npm versions of custom-plugins-request-factory are flagged malicious: 35.5.4. Treat any of these as compromised.

How do I remediate custom-plugins-request-factory if I installed it?

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.

I already installed custom-plugins-request-factory — how do I know if it already compromised me?

If custom-plugins-request-factory 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 custom-plugins-request-factory part of a known attack campaign?

Yes — custom-plugins-request-factory is associated with the IN-MAL-2026-015104 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 custom-plugins-request-factory across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for custom-plugins-request-factory (version 35.5.4).

Malicious package

custom-plugins-request-factorynpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

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)

MAL-2026-12668

Immediate action

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

npm uninstall custom-plugins-request-factory

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

1 flagged

35.5.4

Indicators of compromise (SHA-256)

c25a4c4f3672ed82aa59bcac3fff0c6eadcb3eb35add0f52155c4436cba62c52

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for custom-plugins-request-factory (version 35.5.4).
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 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. custom-plugins-request-factory on npm has been identified as a malicious package (version 35.5.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015104

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database