Which versions of devplatform-ui-notification are malicious?

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

How do I remediate devplatform-ui-notification if I installed it?

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

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

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

Malicious package

devplatform-ui-notificationnpm

devplatform-ui-notification is a confirmed malicious npm package (MAL-2026-13270) that executes malicious code on install (malicious version 35.3.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in devplatform-ui-notification (npm)

MAL-2026-13270

Immediate action

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

npm uninstall devplatform-ui-notification

What this malware does

index.js unconditionally requires./compat on load, which selects a platform-specific asset path (linux/darwin/win32) and downloads bytes over HTTPS from string-obfuscated Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev) with a DNS-TXT base64 fallback channel under *.dl.wel1.ru. The downloaded payload is written to /var/tmp (or the Windows TEMP directory) under a disguised name resembling dotnet_diag.exe /.cache_, chmodded to 0755, and spawned detached via /bin/sh -c '<file> &' or cmd /c start with stdio ignored. Destination hosts are assembled from split string fragments (e.g. ["oob-worker.cf","103-070",".worker","s.","de","v"].join("")) and child_process / chmodSync are required via string concatenation (require("child_" + "process"), fs["chmod" + "Sync"]) to evade static URL and API scanning. The same download-then-execute chain is duplicated in lib/telemetry.js (81KB). There is no version pinning, no hash or signature verification, and the destinations are unrelated to a UI notification library.

Malicious versions

1 flagged

35.3.6

Indicators of compromise (SHA-256)

74230ed898152bc75d702938fcac9bd53e13ff7100120b44c5944bb8226225f7

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 devplatform-ui-notification (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 devplatform-ui-notification across your stack and pipelines.
If you installed it — respond
Remove devplatform-ui-notification 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 devplatform-ui-notification 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 devplatform-ui-notification 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. devplatform-ui-notification 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-015719

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks devplatform-ui-notification-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