Which versions of dolyame-ui-constants are malicious?

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

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

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

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

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

Malicious package

dolyame-ui-constantsnpm

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

Malicious code in dolyame-ui-constants (npm)

MAL-2026-13149

Immediate action

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

npm uninstall dolyame-ui-constants

What this malware does

On require of the package, index.js loads _support.js which assembles Cloudflare Workers hostnames via split-string concatenation (["oob-work","er.cf101-adf.workers.d","ev"].join(""), plus cf102-baf and cf103-070 variants) with a DNS fallback to *.dl.wel1.ru. It downloads a platform-specific binary, writes it to /tmp or %TEMP% under deceptive names (.cache_<hex> on Linux/macOS, dotnet_diag_<hex>.exe on Windows to mimic a Microsoft diagnostic tool), chmods it 0755, and spawns it detached via cp.spawn("/bin/sh",["-c",fp+" &"],{detached:true}) (and spawn("cmd",...) on Windows). The payload is unsigned, unpinned, and unverified. Environment variables named DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, and DO_NOT_TRACK frame the behavior as telemetry, but the destinations, filename disguises, and execution pattern are dropper mechanics rather than telemetry. A second, larger parallel dropper implementation lives in lib/telemetry.js (base64-decoded buffers, fs["chmod"+"Sync"], split-string require("child_"+"process"), cp.spawn('/bin/sh',['-c',filePath+' &'])), staged for activation. Installing or requiring this package causes attacker-controlled code to execute on the installer's host.

Malicious versions

1 flagged

35.5.9

Indicators of compromise (SHA-256)

55e6fcb5f8524548ac64acbf658f83a4b610700e0201d3ffe225fcd9d34f7ae2

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

Campaign

IN-MAL-2026-015630

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dolyame-ui-constants-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