Which versions of dolyame-ui-inputdate are malicious?

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

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

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

If dolyame-ui-inputdate was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is dolyame-ui-inputdate part of a known attack campaign?

Yes — dolyame-ui-inputdate is associated with the IN-MAL-2026-017045 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-inputdate across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dolyame-ui-inputdate (version 35.8.1).

Malicious package

dolyame-ui-inputdatenpm

Advisory published Aug 7, 2026Updated Aug 7, 2026

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

MAL-2026-13577

Immediate action

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

npm uninstall dolyame-ui-inputdate

What this malware does

On require()/import, index.js loads./ext.js which selects a platform-specific remote endpoint, downloads an opaque binary via HTTPS from string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev), with a base64-over-DNS-TXT fallback channel across sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The downloaded bytes are written to a hidden temp file (.cache<rand> / dotnet_diag_<rand>.exe), chmod 0755, and spawned detached via /bin/sh -c or cmd. Hostname reconstruction from split-string arrays and the DNS covert-channel fallback demonstrate deliberate evasion. The package's stated purpose ('API client wrappers') does not correspond to any of this behavior.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

338935a6ea459d3f1882101939a348b871a9cf59d49003f5e04eb65afd60c484

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dolyame-ui-inputdate (version 35.8.1).
If you installed it — respond
Remove dolyame-ui-inputdate 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-inputdate was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dolyame-ui-inputdate 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-017045

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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