Malicious Code Injection in satisfactory_barnacle_z3n Package

satisfactory_barnacle_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96441: Malicious code in satisfactory_barnacle_z3n (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 satisfactory_barnacle_z3n package is part of the npm ecosystem, typically used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages that flood the npm registry. These packages are designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in satisfactory_barnacle_z3n arises from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores and pollute the npm registry with numerous derivative packages. The source of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall satisfactory_barnacle_z3n

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 avoid using the satisfactory_barnacle_z3n package and replace it with a trusted alternative. Always validate the packages you include in your project to ensure they do not contain malicious code.

Conclusion

The satisfactory_barnacle_z3n package poses a significant security risk due to its malicious code designed to exploit npm's publishing system. It is crucial to remove this package from your project and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for satisfactory_barnacle_z3n →

Share this vulnerability

FAQ

satisfactory_barnacle_z3n is an npm package that has been identified as malicious, designed to manipulate npm's publishing system for fraudulent purposes.

The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.

If you have installed satisfactory_barnacle_z3n, you should uninstall it immediately using 'npm uninstall satisfactory_barnacle_z3n' and review your project's dependencies for other potential vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground without any signup.

Yes, you should look for well-maintained and widely used packages that serve the same purpose as satisfactory_barnacle_z3n, ensuring they have a good reputation and community support.

How To Fix

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

npm uninstall satisfactory_barnacle_z3n

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