Malicious Code Injection in literary_stork-apptea Package

literary_stork-apptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105261: Malicious code in literary_stork-apptea (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 literary_stork-apptea package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the npm registry but has been compromised to include malicious scripts. These scripts are intended to manipulate package metadata and inflate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in the literary_stork-apptea package stems from the presence of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which leads to the pollution of the npm registry. The malicious payload is part of a broader scheme to exploit the npm ecosystem for token rewards, posing risks such as unauthorized access to sensitive data and potential damage to developer reputations.

How To Fix

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

npm uninstall literary_stork-apptea

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 literary_stork-apptea package from your project by executing: npm uninstall literary_stork-apptea. This will prevent the execution of any malicious scripts associated with the package.

Conclusion

The literary_stork-apptea package contains a serious vulnerability due to malicious code that alters package metadata and can compromise your project. It is crucial to update or remove the package to protect your application from potential threats.

See every vulnerability recorded for literary_stork-apptea →

Share this vulnerability

FAQ

The literary_stork-apptea package is an npm package that is part of a token reward campaign but has been compromised to include malicious code.

The malicious code modifies your package.json file, potentially exposing sensitive information and damaging your project's integrity.

You should uninstall the package immediately and check for any unauthorized changes in your project.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

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 literary_stork-apptea

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