Malicious Code Injection in tired_narwhal-appteadev Package

tired_narwhal-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109716: Malicious code in tired_narwhal-appteadev (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The tired_narwhal-appteadev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of numerous derivative packages. The malicious behavior includes modifying package metadata and republishing variants to pollute the npm registry.

Vulnerability Detail

The vulnerability originates from the package being part of a token reward campaign that floods npm with malicious packages. It contains scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior can lead to the unintentional exposure of sensitive information and the pollution of the npm registry, affecting developers and users relying on legitimate packages.

How To Fix

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

npm uninstall tired_narwhal-appteadev

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, avoid using the tired_narwhal-appteadev package and consider replacing it with a reputable alternative. Regularly audit your package dependencies to ensure no malicious packages are included.

Conclusion

The tired_narwhal-appteadev package poses a significant risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is essential to remove this package and monitor your dependencies for potential vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for tired_narwhal-appteadev →

Share this vulnerability

FAQ

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

You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without needing to sign up.

You should uninstall the package immediately using the command: npm uninstall tired_narwhal-appteadev.

Yes, the vulnerability can lead to the exposure of sensitive information and the pollution of the npm registry, affecting the integrity of your project.

Regularly audit your dependencies, use trusted packages, and stay informed about known vulnerabilities in the npm ecosystem.

How To Fix

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

npm uninstall tired_narwhal-appteadev

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