Which versions of dolyame-ui-inputtime are malicious?

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

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

Remove dolyame-ui-inputtime 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.

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

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

Yes — dolyame-ui-inputtime is associated with the IN-MAL-2026-016985 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-inputtime 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-inputtime (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-inputtime across your stack and pipelines.

Malicious package

dolyame-ui-inputtimenpm

dolyame-ui-inputtime is a confirmed malicious npm package (MAL-2026-13586) 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-inputtime (npm)

MAL-2026-13586

Immediate action

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

npm uninstall dolyame-ui-inputtime

What this malware does

On require('dolyame-ui-inputtime'), index.js loads./loader.js which fetches a platform-specific executable from hardcoded Cloudflare Workers hosts (oob-worker.cf101-.workers.dev, oob-worker.cf102-.workers.dev, oob-worker.cf103-*.workers.dev), with a DNS-TXT covert-channel fallback under *.dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru): dns.resolveTxt is used to fetch a chunk count and base64-encoded payload chunks that are concatenated and decoded. The fetched bytes are written to /tmp or %TEMP% under masquerade names (.cache<rand> on POSIX, dotnet_diag_<rand>.exe on Windows), chmod 0755'd, and spawned detached via /bin/sh -c '<path> &' or cmd /c start, with.unref() to survive the parent process. Hostnames are reconstructed at runtime from array.join to evade static analysis, and dangerous APIs are resolved via string concatenation (require('child_' + 'process'), fs['chmod' + 'Sync']). The same dropper logic is duplicated in lib/telemetry.js under an SDK_NAME='apm.node' cover. Manifest name and description ('Monitoring and observability SDK') do not match the shipped behavior; the package name has no relation to the code.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

19ce8608ab1a5fcb21175b9bb64053362c941cf3ffefe754caf02c8000b44fb5

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-ui-inputtime (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-inputtime across your stack and pipelines.
If you installed it — respond
Remove dolyame-ui-inputtime 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-inputtime 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-inputtime 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-inputtime on npm has been identified as a malicious package (version 35.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016985

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database