Which versions of dolyame-ui-portal are malicious?

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

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

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

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

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

Malicious package

dolyame-ui-portalnpm

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

Malicious code in dolyame-ui-portal (npm)

MAL-2026-13176

Immediate action

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

npm uninstall dolyame-ui-portal

What this malware does

index.js unconditionally requires./bridge on load. bridge.js assembles Cloudflare Workers hostnames (oob-worker.cf10{0-3}-*.workers.dev) and a DNS-TXT discovery domain (sdk.dl.wel1.ru) from array-join string splits to hide them from static scanners, downloads a platform-specific binary over HTTPS, writes it to /var/tmp or %TEMP% under a cover-story name (.cache<hex> / dotnet_diag<hex>.exe), chmods it 0755, and detached-spawns it via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}) or spawn('cmd',...). The dropper is gated by opt-out env vars (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) to evade sandboxed analysis. A parallel dropper is bundled at lib/telemetry.js under an 'Analytics SDK' cover story (base64-decoded payload chunks, chmod 755, /bin/sh -c spawn) that is not reached from the current require chain. Requiring or installing this package results in execution of attacker-controlled code from non-publisher infrastructure.

Malicious versions

1 flagged

35.3.6

Indicators of compromise (SHA-256)

5cf459576a54fb40358c8e22e4283559ce302a6d6e2c6cd545b48ae9be4d8ccf

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

Campaign

IN-MAL-2026-015599

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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