dolyame-ui-inputsearchtagged
This report shows the evidence for dolyame-ui-inputsearchtagged@35.8.1, the only known version.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-13583 confirms this npm version as malicious.
Advisory
MAL-2026-13583
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in dolyame-ui-inputsearchtagged (npm)
Details
On require of the package, _init.js selects a platform-specific payload, downloads opaque bytes over HTTPS from a rotating set of anonymous Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), with a fallback covert channel using DNS TXT lookups against sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru to reassemble a base64 payload. The downloaded bytes are written to /var/tmp/.cache_<hex> on Linux or %TEMP%/dotnet_diag_<hex>.exe on Windows, chmod 0755, and spawned detached via spawn("/bin/sh") or spawn("cmd"). Hostnames are constructed from split-string arrays joined at runtime to evade static analysis, and file names (.cache_<hex>, dotnet_diag_<hex>.exe, /tmp/.analytics_state) plus DISABLE_TELEMETRY/DO_NOT_TRACK env checks are used as a telemetry cover story. There is no pinning, no integrity check, and the destinations are unrelated to any legitimate publisher; installing or importing the package results in full-host code execution under attacker control.
References
Source & flagged code
0 flaggedNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to dolyame-ui-inputsearchtagged@35.8.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-ui-inputsearchtagged@35.8.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.