Malicious Code Injection in yearling_takin_z3n Package

yearling_takin_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97486: Malicious code in yearling_takin_z3n (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 yearling_takin_z3n package is part of the npm ecosystem, primarily 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 have malicious intents. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially harming developers and users alike.

Vulnerability Detail

The vulnerability in the yearling_takin_z3n package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names and continuously republishes variants to pollute the npm registry. This behavior can lead to a loss of trust in the npm ecosystem and can inflate developer reputation scores fraudulently, impacting the integrity of the software supply chain.

How To Fix

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

npm uninstall yearling_takin_z3n

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 remove the yearling_takin_z3n package from your project by executing: 'npm uninstall yearling_takin_z3n'. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The yearling_takin_z3n package poses a significant risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to take immediate action by removing the package and monitoring for updates to maintain the integrity of their applications.

See every vulnerability recorded for yearling_takin_z3n →

Share this vulnerability

FAQ

The yearling_takin_z3n package is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

This vulnerability can lead to unauthorized changes in your package.json file, potentially compromising your application and its dependencies.

You should uninstall the yearling_takin_z3n package immediately and monitor for any updates or patches that may be released.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Vulert is a tool that monitors open-source vulnerabilities in your software using just the package-lock.json file, providing real-time alerts.

How To Fix

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

npm uninstall yearling_takin_z3n

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