Malicious Code Injection in verify-taicuil-busauna Package

verify-taicuil-busauna Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170489: Malicious code in verify-taicuil-busauna (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-taicuil-busauna package is part of a larger ecosystem within the npm registry, primarily used for various JavaScript applications. It has been identified as part of a token reward campaign that aims to manipulate developer reputation scores. This package, like others in the campaign, is designed to automatically generate and publish derivative packages, which can lead to a polluted npm registry and potential security risks for developers using these packages.

Vulnerability Detail

The vulnerability stems from malicious code embedded in the verify-taicuil-busauna package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are often themed around Indonesian culture. The malicious payload continuously republishes these variants, leading to an inflated presence in the npm registry. This can result in developers inadvertently using compromised packages, exposing their applications to security risks and potential data breaches.

How To Fix

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

npm uninstall verify-taicuil-busauna

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, consider using a package-lock.json file to lock your dependencies to known safe versions. This can prevent the installation of the compromised package until a fix is available.

Conclusion

The verify-taicuil-busauna package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised versions. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your applications.

See every vulnerability recorded for verify-taicuil-busauna →

Share this vulnerability

FAQ

It is a package in the npm registry that has been identified as part of a malicious campaign to inflate developer reputation scores.

Using this package can expose your application to security risks, including data breaches and the introduction of malicious code.

You should uninstall the package immediately using the command: npm uninstall verify-taicuil-busauna.

Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.

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

How To Fix

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

npm uninstall verify-taicuil-busauna

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