Malicious Code Injection in maya-jus36-miaww Package

maya-jus36-miaww Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88349: Malicious code in maya-jus36-miaww (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 maya-jus36-miaww package is part of the npm ecosystem, typically used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that can inflate developer reputation scores. This package, like others in the campaign, is designed to automatically generate and publish derivative packages, posing a risk to developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the maya-jus36-miaww package originates from its malicious design, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on this package. The malicious payload can affect the reputation of developers and the reliability of the npm ecosystem.

How To Fix

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

npm uninstall maya-jus36-miaww

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 maya-jus36-miaww package and any packages that depend on it. Regularly audit your dependencies using 'npm audit' to identify and address vulnerabilities.

Conclusion

The maya-jus36-miaww package contains a serious vulnerability due to its malicious design, which can compromise the integrity of the npm registry and the applications that depend on it. It is crucial to remove this package and monitor your dependencies for any vulnerabilities.

See every vulnerability recorded for maya-jus36-miaww →

Share this vulnerability

FAQ

The maya-jus36-miaww package is an npm package associated with a token reward campaign that generates and publishes derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the security and integrity of applications that rely on this package.

You should uninstall the maya-jus36-miaww package immediately and check your package-lock.json for any references to it.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall maya-jus36-miaww

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