Malicious code in dolyame-ui-cardlogo (npm)
The npm package dolyame-ui-cardlogo contained malicious code that downloads and executes platform-specific binaries from attacker-controlled domains. The package was identified by Amazon Inspector and credited to OpenSSF's malicious-packages repository.
- Disclosed
- Last updated
- Blast radius
- All npm users who installed dolyame-ui-cardlogo
- Ecosystems
- Attack vectors
- Affected entities
- dolyame-ui-cardlogonpm package containing malicious code
The npm package dolyame-ui-cardlogo was found to contain malicious code designed to execute arbitrary binaries on affected systems. Upon load, the package's index.js file requires _polyfill.js, which downloads platform-specific binaries from attacker-controlled hostnames reconstructed at runtime via string-array concatenation.
The malicious code fetches binaries from multiple domains (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with DNS TXT-record fallbacks resolving to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The downloaded binaries are written to temporary directories (/tmp on POSIX systems, %TEMP% on Windows) under disguised names (.cache_ on POSIX, dotnet_diag_.exe on Windows), made executable, and spawned detached via shell commands.
The malicious functionality is obfuscated through helper functions with 'telemetry' and 'analytics' naming conventions, with environment variable checks for DISABLE_TELEMETRY and ANALYTICS_OPT_OUT that have no legitimate purpose for a UI component package. This behavior is entirely inconsistent with the package's stated purpose as a UI library.
Indicators of compromise
- Packages
- dolyame-ui-cardlogo
- Domains
- oob-worker.cf99-9b3.workers.dev
- oob-worker.cf100-416.workers.dev
- oob-worker.cf101-adf.workers.dev
- oob-worker.cf102-baf.workers.dev
- sdk.dl.wel1.ru
- ext.dl.wel1.ru
- pkg.dl.wel1.ru
- net.dl.wel1.ru
Remediation
- Immediately remove dolyame-ui-cardlogo from all projects and dependencies
- Audit npm package.json and lock files for any presence of dolyame-ui-cardlogo
- Review systems that may have installed this package for signs of unauthorized binary execution or network connections to the identified domains
- Monitor for suspicious processes spawned from /bin/sh or cmd.exe with temporary file execution
- Consider rotating credentials and reviewing system logs for any suspicious activity on affected machines
- Use npm audit to identify any other potentially malicious packages in your dependency tree
Sources
- GitHub Advisory GHSA-689h-gvpf-9mh5 · GitHub Advisory Database
Cite this entry
"Malicious code in dolyame-ui-cardlogo (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-dolyame-ui-cardlogo-npm-1vofl0
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in chlklib
Malware was discovered in the npm package chlklib, resulting in full system compromise of any computer with the package installed or running. All affected systems should be considered fully compromised and all secrets and keys rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malware in alphazone
The npm package alphazone contained malware that provided full system compromise to attackers. Any computer with the package installed or running should be considered fully compromised.
npmCompromised package - containedcritical
Malware in chai-as-deployer
Malware was discovered in the npm package chai-as-deployer, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - containedcritical
Malware in checkout-common-tokens
Malware was discovered in the npm package checkout-common-tokens. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package