This report shows the evidence for dsh-notify-focus@0.5.0. 3 of 6 known versions are blocked or flagged. The newest version, 0.7.3, is allowed.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-18748 identifies this version as malicious and supplies the Firewall block. LPM AI review remains unresolved.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-18748 confirms this npm version as malicious.
Advisory
MAL-2026-18748
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in dsh-notify-focus (npm)
Details
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
LPM's AI review of this version remains unresolved. The OpenSSF/OSV advisory supplies the block.
The inspected JavaScript supports a local notification and window-focus flow, with no confirmed attack behavior. The shipped executable is used by that flow, and its behavior could not be inspected, so the package requires manual review.
Static reason
No blocking static signals were detected.
Trigger
Windows launches the helper when a notification activation invokes the registered protocol.
Impact
The helper’s effects cannot be established from the inspected source, so malicious behavior is neither confirmed nor ruled out.
Mechanism
The host selects the packaged executable as its focus helper; available offline analysis could not inspect the executable’s behavior.
The versions list below shows the verdict for each recorded version.
Avoid installing dsh-notify-focus@0.5.0. 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.