Which versions of dolyame-ui-textarea are malicious?

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

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

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

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

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

Malicious package

dolyame-ui-textareanpm

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

Malicious code in dolyame-ui-textarea (npm)

MAL-2026-13194

Immediate action

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

npm uninstall dolyame-ui-textarea

What this malware does

The package's main entry unconditionally requires./loader.js on load. loader.js assembles mirror hostnames from split string arrays to build a set of .workers.dev endpoints (e.g. oob-worker.cf10x-.workers.dev), fetches a platform-specific binary over https.get, and falls back to base64-chunked DNS TXT records under *.dl.wel1.ru subdomains when the HTTP mirrors are unavailable. The fetched bytes are written to /var/tmp or %TEMP% under masquerade filenames (.cache<rand> on Unix, dotnet_diag<rand>.exe on Windows), chmodded to 0755, and spawned detached via /bin/sh -c or cmd.exe with stdio ignored and unref(). Environment variables named DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK and a cache filename.analytics_state disguise the dropper as telemetry. A second variant of the same dropper (base64 chunk assembly, chmod 0755 via dynamic property name fs['chmod'+'Sync'], detached /bin/sh spawn) is bundled in lib/telemetry.js under an 'analytics SDK' cover story. The package name resembles a UI component library but ships no textarea functionality; its only on-load behavior is the drop-and-execute chain.

Malicious versions

1 flagged

35.3.4

Indicators of compromise (SHA-256)

24932ddb1e2cd6672b95aae062c330f9aec9d68ee293488d54d195fbbf0acc52

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

Campaign

IN-MAL-2026-015574

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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