Malicious Code Injection in physical_possum-apptea: npm Package Vulnerability
Summary
MAL-2025-107076: Malicious code in physical_possum-apptea (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The 'physical_possum-apptea' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'physical_possum-apptea' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random Indonesian-themed package names and continuously republishes these variants, leading to pollution of the npm registry. This behavior can result in developers unknowingly installing compromised packages, which may lead to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall physical_possum-appteaIf 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 avoid using the 'physical_possum-apptea' package until a patched version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'physical_possum-apptea' package has been identified as containing malicious code that poses a significant risk to developers using npm. It is crucial to stay informed about such vulnerabilities and take proactive measures to secure your applications. Regular updates and monitoring tools like Vulert can help mitigate these risks.
See every vulnerability recorded for physical_possum-apptea →
FAQ
The vulnerability involves malicious code that modifies package.json files and republishes compromised packages to the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Using the affected package can lead to security breaches, installation of compromised software, and loss of trust in the npm ecosystem.
Regularly update your dependencies and use tools like Vulert to monitor for vulnerabilities in your packages.
Remove the package from your project and update to a patched version if available. Review your project for any potential security issues caused by the compromised package.
