dolyame-ui-memoizeweaknpm
dolyame-ui-memoizeweak is a confirmed malicious npm package (MAL-2026-13589) that executes malicious code on install (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-ui-memoizeweak (npm)
What this malware does
On require of the package, index.js loads./helpers.js which downloads a platform-specific executable from one of several hardcoded Cloudflare Workers endpoints (oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev), with a DNS-TXT covert-channel fallback via sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under cover names such as dotnet_diag.exe and.cache_, chmodded 0755, and detach-spawned via cp.spawn('/bin/sh', ['-c', path + ' &'], {detached:true}). Hostnames and sensitive API names (child_process, chmodSync) are reassembled at runtime from split string fragments to evade static analysis (e.g. ['oob-work','er.cf9','9-9b3.workers.d','ev'].join(''), require('child_'+'process')). A second, redundant dropper path in lib/telemetry.js base64-decodes fetched chunks, writes an 'extension' file, chmods 0755, and spawns /bin/sh on the result under an 'Analytics SDK' framing. No version pinning, no hash or signature verification, no legitimate purpose consistent with the package's declared name.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-memoizeweak (version 35.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-ui-memoizeweak across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-memoizeweak 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 dolyame-ui-memoizeweak 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-memoizeweak 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks dolyame-ui-memoizeweak-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.