Malicious Code Injection in verify-taic-malasulu Package

verify-taic-malasulu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170485: Malicious code in verify-taic-malasulu (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 verify-taic-malasulu package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is implicated in a malicious campaign that aims to exploit npm's publishing system. It is designed to generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards in the tea.xyz protocol.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the verify-taic-malasulu package. This code modifies the package.json file to remove private flags, alters version numbers, and creates random package names, leading to the continuous republishing of these variants. This behavior can pollute the npm registry, making it difficult for developers to find legitimate packages and potentially compromising their applications.

How To Fix

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

npm uninstall verify-taic-malasulu

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 verify-taic-malasulu package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.

Conclusion

The verify-taic-malasulu package has been identified as containing malicious code that can compromise your application and pollute the npm registry. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities using tools like Vulert.

See every vulnerability recorded for verify-taic-malasulu →

Share this vulnerability

FAQ

The verify-taic-malasulu package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The malicious code can modify your package.json file, leading to potential security risks and the pollution of the npm registry with illegitimate packages.

You should uninstall the verify-taic-malasulu package immediately and check for any alternative packages that can fulfill your requirements.

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

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 verify-taic-malasulu

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