MAL-2026-18202: Malicious code in the npm package sdk-utils-testmetest
Summary
MAL-2026-18202: Installing or running the package can fully compromise a computer, exposing stored secrets and keys and potentially leaving additional malicious software behind. Affected versions are not published. 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
sdk-utils-testmetest is a package in the npm ecosystem. The supplied advisory identifies it as containing malicious code. The available information does not describe the package’s intended functionality or where it is used, so those details are not published.
Vulnerability Detail
The package can fully compromise a computer when installed or running. This is embedded malicious code, classified as CWE-506. The advisory warns that secrets and keys stored on an affected computer should be rotated from a different computer. Removing the package may not remove other malicious software that resulted from its installation, because an outside entity may have gained full control.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sdk-utils-testmetestIf 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 sdk-utils-testmetest and rotate all secrets and keys stored on the affected computer immediately from a different computer. Because the computer may have been fully compromised, removing the package alone cannot guarantee that all resulting malicious software is removed.
Conclusion
No fixed version is published for sdk-utils-testmetest. Remove the package and rotate exposed secrets and keys from a different computer; removal alone may not eliminate all 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 sdk-utils-testmetest →
FAQ
All versions of sdk-utils-testmetest are affected; the published range begins at the introduction of the package.
sdk-utils-testmetest can fully compromise a computer, expose stored secrets and keys, and potentially leave additional malicious software behind.
Yes. sdk-utils-testmetest is identified as containing malicious code, and no fixed version is published.
Remove sdk-utils-testmetest, rotate stored secrets and keys from a different computer, and account for possible remaining malicious software.
Check package-lock.json for sdk-utils-testmetest. Vulert can scan a manifest or SBOM and monitor the dependency at Vulert Scanner.
