Malicious Code Injection in miracle-diook-ujakaubaik1 Package

miracle-diook-ujakaubaik1 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160502: Malicious code in miracle-diook-ujakaubaik1 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The miracle-diook-ujakaubaik1 package is part of the npm ecosystem and has been associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the miracle-diook-ujakaubaik1 package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The malicious payload is designed to continuously republish variants of the package, which can result in significant security risks for developers who unknowingly use these compromised packages.

How To Fix

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

npm uninstall miracle-diook-ujakaubaik1

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 miracle-diook-ujakaubaik1 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package.json file does not include any references to this malicious package.

Conclusion

The miracle-diook-ujakaubaik1 package contains malicious code that poses significant security risks to developers using npm. It is crucial to uninstall this package and monitor for any similar vulnerabilities in your dependencies. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for miracle-diook-ujakaubaik1 →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file, removes private flags, and can lead to the pollution of the npm registry, posing security risks.

You should uninstall the package immediately using 'npm uninstall miracle-diook-ujakaubaik1' and check for any other affected packages.

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

You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall miracle-diook-ujakaubaik1

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