MAL-2026-18200: Malicious code in @seggy116/next-diff can compromise computers
Summary
MAL-2026-18200: Installation or execution can give an outside entity full control of the affected computer, exposing stored secrets and keys. Affects @seggy116/next-diff versions 0.3.0. 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
@seggy116/next-diff is an npm package in the JavaScript ecosystem. The supplied advisory identifies it as containing malicious code. The available record does not describe the package’s intended functionality or where it is used, so those details are not published.
Vulnerability Detail
The malicious code can give an outside entity full control of a computer where @seggy116/next-diff is installed or running. The advisory classifies the issue as embedded malicious code (CWE-506) and warns that stored secrets and keys may be exposed. Removing the package does not guarantee that other malicious software introduced during installation has been removed.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @seggy116/next-diffIf 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
Documented workaround: Remove @seggy116/next-diff and rotate all secrets and keys stored on the affected computer from a different computer. Because the computer may have been fully controlled by an outside entity, package removal alone may not remove other malicious software.
Conclusion
No fixed version is published for @seggy116/next-diff. Remove the package and treat any computer where it was installed or running as compromised; rotate stored secrets and keys from a different computer. Removal alone may not eliminate other malicious software. Vulert monitors the dependencies in package-lock.json and alerts when a new vulnerability affects them; check an application at https://vulert.com/scanner.
See every vulnerability recorded for @seggy116/next-diff →
FAQ
@seggy116/next-diff version 0.3.0 is identified as malicious in the supplied record.
@seggy116/next-diff can give an outside entity full control of a computer and expose stored secrets and keys.
No fixed version is published for @seggy116/next-diff; remove the package and follow the documented response steps.
Treat the computer as compromised, rotate stored secrets and keys from a different computer, and remove @seggy116/next-diff.
Check package-lock.json manually for @seggy116/next-diff. Vulert can scan a manifest or SBOM and monitor the dependency at Vulert Scanner.
