Malicious Code Injection in Squealing Pinniped Replicate Automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109052: Malicious code in squealing_pinniped_replicate_automation (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 'squealing_pinniped_replicate_automation' package is part of a broader ecosystem within npm, often associated with the tea.xyz token reward campaign. This package is designed to automate certain tasks, but it has been compromised to include malicious functionalities that can harm developers and the integrity of the npm registry.

Vulnerability Detail

This vulnerability originates from the malicious intent behind the package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The primary risk is the pollution of the npm registry with these derivative packages, which can lead to reputation inflation for malicious actors and potentially expose users to further security risks.

How To Fix

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

npm uninstall squealing_pinniped_replicate_automation

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 affected package by removing it from your dependencies and replacing its functionality with a trusted alternative. Always ensure to audit your dependencies regularly.

Conclusion

The 'squealing_pinniped_replicate_automation' package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential to remove this package from your projects and monitor your dependencies to maintain security.

See every vulnerability recorded for squealing_pinniped_replicate_automation →

Share this vulnerability

FAQ

The package contains malicious code that modifies package.json files and floods the npm registry with derivative packages.

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.

You should uninstall the package immediately and check for any dependencies that may rely on it.

Yes, using this package can lead to the pollution of the npm registry and may expose your project to further security risks.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.

How To Fix

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

npm uninstall squealing_pinniped_replicate_automation

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