Malicious Code Injection in wati-getuk8-wekto Package

wati-getuk8-wekto Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-92013: Malicious code in wati-getuk8-wekto (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The wati-getuk8-wekto package is part of the npm ecosystem, often used for various JavaScript applications. This package has been identified as part of a larger campaign that exploits npm's publishing mechanisms. It is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names, which can lead to a polluted npm registry.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the wati-getuk8-wekto package. This code modifies the package.json file by removing private flags and changing version numbers, allowing the package to continuously republish itself with random names. This behavior can lead to significant security risks, including the potential for dependency confusion attacks, where developers may inadvertently use compromised packages, leading to data breaches or system compromises.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall wati-getuk8-wekto

If 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 wati-getuk8-wekto package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Conclusion

The wati-getuk8-wekto package poses a significant security risk due to its malicious code that modifies package metadata and republish behavior. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities to maintain application security.

See every vulnerability recorded for wati-getuk8-wekto →

Share this vulnerability

FAQ

The wati-getuk8-wekto package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the inclusion of compromised packages in your application, which may result in security breaches or data leaks.

You should uninstall the wati-getuk8-wekto package immediately and check your project for any dependencies that may have been affected.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall wati-getuk8-wekto

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback