Malicious Code Detected in @get-wrecked/overlay: A Critical Security Alert
Summary
MAL-2026-1241: Malicious code in @get-wrecked/overlay (npm). Affects @get-wrecked/overlay versions 1.0.22. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The package @get-wrecked/overlay is an npm package designed for overlay functionalities in web applications. It is utilized by developers to enhance user interfaces and manage component overlays effectively. However, version 1.0.22 of this package has been flagged for containing malicious code that executes harmful commands, posing a significant security risk to applications that incorporate it.
Vulnerability Detail
The vulnerability in @get-wrecked/overlay stems from its malicious behavior, where it executes commands that can compromise the security of the host application. This issue was identified by the OpenSSF Package Analysis project, which found that the package version 1.0.22 contains code that could lead to unauthorized access or data manipulation. The ramifications of this vulnerability can include data breaches, loss of user trust, and potential legal implications for developers who fail to address it.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @get-wrecked/overlayIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, you can avoid using the @get-wrecked/overlay package in your project until a secure version is released. If you require similar functionality, consider using alternative packages that are known to be secure.
Conclusion
The discovery of malicious code in the @get-wrecked/overlay package highlights the importance of regularly auditing third-party dependencies. Developers should take immediate action to remove the affected package and seek alternatives while staying vigilant for updates from the maintainers.
See every vulnerability recorded for @get-wrecked/overlay →
FAQ
The malicious code executes commands that can compromise the security of the host application, potentially leading to unauthorized access or data manipulation.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without needing to sign up.
Currently, there is no patched version available. It is recommended to uninstall the package until a secure version is released.
You should uninstall the package immediately and look for alternative solutions that provide similar functionality without the security risks.
You can use tools like Vulert to monitor your project's dependencies for vulnerabilities and receive real-time alerts.
