Which versions of dolyame-ui-react-dom-wrapper are malicious?

The following npm versions of dolyame-ui-react-dom-wrapper are flagged malicious: 35.8.9. Treat any of these as compromised.

How do I remediate dolyame-ui-react-dom-wrapper if I installed it?

dolyame-ui-react-dom-wrapper 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 dolyame-ui-react-dom-wrapper — how do I know if it already compromised me?

If dolyame-ui-react-dom-wrapper 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 dolyame-ui-react-dom-wrapper part of a known attack campaign?

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

Malicious package

dolyame-ui-react-dom-wrappernpm

dolyame-ui-react-dom-wrapper is a confirmed malicious npm package (MAL-2026-13178) that opens a backdoor for remote access (malicious version 35.8.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-react-dom-wrapper (npm)

MAL-2026-13178

Immediate action

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

npm uninstall dolyame-ui-react-dom-wrapper

What this malware does

On require of the package's main entry, helpers.js selects a platform-specific target path, fetches an opaque binary over HTTPS from author-controlled Cloudflare Worker subdomains (oob-worker.cf99-9b3.workers.dev, cf103-070/cf100-416/cf102-baf.workers.dev) with a DNS-based fallback to sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, writes the bytes to /tmp or %TEMP% under disguised names ('.cache<rnd>', 'dotnet_diag_<rnd>.exe'), chmods 0755 on Unix, and detached-spawns the file via '/bin/sh -c <path> &' or 'cmd /c start'. C2 hostnames and sensitive API names (child_process, chmodSync) are assembled at runtime from split-string arrays joined with '' to defeat static analysis. A second copy of the same fetch → base64 → chmod 0755 → detached-spawn chain, with identical string-concatenation obfuscation of 'child_process', is bundled in lib/telemetry.js as a parallel dropper. Any installer that requires this package executes attacker-controlled binaries with the user's privileges.

Malicious versions

1 flagged

35.8.9

Indicators of compromise (SHA-256)

3c3f53ba29324123e792649baa012f91a2a980590dea560599490d8020b6274b

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 dolyame-ui-react-dom-wrapper (version 35.8.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-react-dom-wrapper across your stack and pipelines.
If you installed it — respond
dolyame-ui-react-dom-wrapper 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 dolyame-ui-react-dom-wrapper 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 dolyame-ui-react-dom-wrapper 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. dolyame-ui-react-dom-wrapper on npm has been identified as a malicious package (version 35.8.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015595

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-react-dom-wrapper-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

Explore

All malware advisories How O3 detects malware Vulnerability database