Malicious Code Injection in atomic_pinniped_z3n: Exploiting npm Packages
Summary
MAL-2025-99652: Malicious code in atomic_pinniped_z3n (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 package 'atomic_pinniped_z3n' 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 floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated scripts that publish numerous variants with randomized names.
Vulnerability Detail
The vulnerability in 'atomic_pinniped_z3n' originates from its association with the tea.xyz token reward campaign. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of these variants. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall atomic_pinniped_z3nIf 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 'atomic_pinniped_z3n' package and replace it with an alternative package that provides similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'atomic_pinniped_z3n' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies to maintain the security of their applications.
See every vulnerability recorded for atomic_pinniped_z3n →
FAQ
The main issue is that it contains malicious code designed to manipulate package.json files and flood the npm registry with compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
You should immediately uninstall the package and check for any dependencies that may have been affected by it.
While specific exploits have not been detailed, the manipulation of package.json files can lead to broader security issues in applications that rely on these packages.
Regularly audit your dependencies, use trusted sources for packages, and consider employing tools like Vulert to monitor for vulnerabilities in real-time.
