Which versions of dolyame-ui-container are malicious?

The following npm versions of dolyame-ui-container are flagged malicious: 35.3.7. Treat any of these as compromised.

How do I remediate dolyame-ui-container if I installed it?

dolyame-ui-container is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed dolyame-ui-container — how do I know if it already compromised me?

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

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

Malicious package

dolyame-ui-containernpm

dolyame-ui-container is a confirmed malicious npm package (MAL-2026-13150) that steals credentials and exfiltrates sensitive data (malicious version 35.3.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dolyame-ui-container (npm)

MAL-2026-13150

Immediate action

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

npm uninstall dolyame-ui-container

What this malware does

On require of the package, index.js loads compat.js, which at module load time downloads a platform-specific binary from hostnames assembled at runtime via string-splitting (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev). If HTTPS mirrors fail, it falls back to a DNS-over-TXT covert channel, resolving TXT records under *.dl.wel1.ru subdomains and base64-decoding the concatenated response into a binary. The fetched payload is written to a disguised path under /tmp or %TEMP% (e.g. dotnet_diag<hex>.exe,.cache_<hex>), chmod 0755, and spawned detached via cmd.exe or /bin/sh -c with no hash or signature verification. Environment variable checks (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and analytics-styled filenames provide cover. The destinations are not the publisher's infrastructure and the retrieval mechanism is inconsistent with any legitimate distribution channel.

Malicious versions

1 flagged

35.3.7

Indicators of compromise (SHA-256)

0b0f03a063fb3a6b8c7605612b587eddfefa6181b85b14654ee93f267dd790e1

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-container (version 35.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-container across your stack and pipelines.
If you installed it — respond
dolyame-ui-container is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If dolyame-ui-container 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-container 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-container on npm has been identified as a malicious package (version 35.3.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015635

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-container-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database