Malicious Code Injection in wild_krill-gooddev Package

wild_krill-gooddev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110915: Malicious code in wild_krill-gooddev (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The wild_krill-gooddev package is part of the npm ecosystem, typically used for various development tasks. However, it has been identified as part of a malicious campaign that exploits npm's package management system. The package is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the wild_krill-gooddev package, which contains malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme associated with the tea.xyz token reward campaign, which aims to manipulate npm's ecosystem for fraudulent gains. The ramifications include the potential for developers to unknowingly install compromised packages, leading to security risks and reputational damage.

How To Fix

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

npm uninstall wild_krill-gooddev

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 measure, you can avoid using the wild_krill-gooddev package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before installation.

Conclusion

The wild_krill-gooddev package poses a significant security risk due to its malicious code designed to manipulate the npm ecosystem. It is essential for developers to be vigilant about the packages they use and to take immediate action to remove any compromised packages from their projects.

See every vulnerability recorded for wild_krill-gooddev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your project.

You should uninstall the wild_krill-gooddev package immediately using the command npm uninstall wild_krill-gooddev.

Yes, tools like Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall wild_krill-gooddev

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