MalwarePublished 22 Oct 2026Updated 29 Oct 2026

sdk-utils-testmetest (npm) · Malicious Code

Affects sdk-utils-testmetestSource GCVE Database

Malicious package : remove sdk-utils-testmetest and rotate any secrets on hosts that installed it.

Data as of 29 Oct 2026, 18:11 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-18202

What to do

Remove sdk-utils-testmetest from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmsdk-utils-testmetest	Affected =1.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package sdk-utils-testmetest version 1.0.0 is identified as malicious software. Although the package itself does not exhibit install-time execution or network activity, its installation compromises the host computer fully. Any secrets or keys stored on the compromised machine should be rotated immediately from a separate, secure device. Removal of the package alone may not eliminate all malicious components due to potential full system compromise.

Impact

Installation of sdk-utils-testmetest@1.0.0 results in full compromise of the affected computer. All secrets and keys stored on the system are at risk and must be rotated immediately from a different, uncompromised device. The compromise is severe enough that simply removing the package does not guarantee removal of all malicious software introduced.

Defensive guidance

Remove the sdk-utils-testmetest@1.0.0 package immediately. Rotate all secrets and keys stored on the compromised system from a separate, secure computer. Due to the potential full system compromise, consider rebuilding the affected system from a known good backup or reinstalling the operating system to ensure complete remediation.

Summary

The sdk-utils-testmetest@1.0.0 npm package is classified as malware. Analysis shows no install-time lifecycle execution or outbound network activity within the package files themselves, and no obfuscated or dynamic code execution patterns were detected. Despite this, the presence of this package on a system indicates a full compromise, likely due to malicious payloads or backdoors introduced post-installation. The package name suggests it may be a test or stub, but this resemblance does not negate the supply-chain threat it poses. Systems with this package installed should be treated as fully compromised.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 18:11 UTC

Technical details

References

Community reviews