Malicious Code Injection in putra-telur3-wekto Package

putra-telur3-wekto Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89617: Malicious code in putra-telur3-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The putra-telur3-wekto package is part of the npm ecosystem, primarily used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the putra-telur3-wekto package originates from its association with a token reward campaign that employs malicious scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that compromise the integrity of the npm registry. This not only affects the reputation of legitimate developers but also poses security risks to users who may unknowingly install these malicious packages.

How To Fix

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

npm uninstall putra-telur3-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 putra-telur3-wekto package and any other packages that may be associated with the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your project's dependencies for vulnerabilities.

Conclusion

The putra-telur3-wekto package poses a significant risk due to its malicious code designed to manipulate npm registry integrity. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your projects.

See every vulnerability recorded for putra-telur3-wekto →

Share this vulnerability

FAQ

putra-telur3-wekto is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

This vulnerability can lead to the installation of malicious code, compromising the security and integrity of your project.

You should remove the putra-telur3-wekto package from your project immediately and monitor for any further updates or patches.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

npm uninstall putra-telur3-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