dolyame-ui-inputphone
This report shows the evidence for dolyame-ui-inputphone@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-13580 confirms this npm version as malicious.
Advisory
MAL-2026-13580
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in dolyame-ui-inputphone (npm)
Details
On require() of the package, index.js loads _runtime.js which downloads a platform-specific binary from a set of Cloudflare Workers endpoints (oob-worker.cf10x-*.workers.dev) with a DNS-TXT chunked fallback to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. Host strings are reconstructed at runtime via array-join (e.g. ['sdk.dl.wel1','.ru'].join('')) to evade static scans, and API references are split (child_'+'process, 'chmod'+'Sync'). The fetched bytes are written to a temp path with a cover-story filename (.cache_*, dotnet_diag_*.exe), chmod 0755 on Unix, and executed detached via cp.spawn('/bin/sh',['-c', filePath+' &']) or spawn('cmd',...) on Windows. No hash or signature verification is performed and the destinations are unrelated to the declared publisher. The package's own main export lib/telemetry.js, presented as a Sentry-like analytics SDK, wraps the same download/write/chmod/spawn primitives — the telemetry facade is cover for the dropper.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to dolyame-ui-inputphone@35.8.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing dolyame-ui-inputphone@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.