Malicious Code Injection in social_crane_z3n Package - npm Vulnerability

social_crane_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98938: Malicious code in social_crane_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The social_crane_z3n package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to generate and publish derivative packages with randomized names, which can lead to reputation inflation for developers involved in the tea.xyz token reward campaign. The malicious nature of this package poses significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the social_crane_z3n package originates from its association with the tea.xyz token reward campaign. It contains scripts that automatically modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially compromise the security of applications relying on this package. The malicious payload can allow unauthorized access to sensitive information and disrupt the normal functioning of dependent applications.

How To Fix

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

npm uninstall social_crane_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 social_crane_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json file is monitored for any unauthorized changes.

Conclusion

The social_crane_z3n package has been identified as a malicious entity within the npm ecosystem, posing significant risks to applications that utilize it. Immediate action is required to remove this package and safeguard your projects from potential exploitation. Utilizing tools like Vulert can enhance your security posture by providing real-time monitoring for vulnerabilities.

See every vulnerability recorded for social_crane_z3n →

Share this vulnerability

FAQ

The social_crane_z3n package is an npm package that has been linked to a malicious campaign aimed at exploiting the npm registry.

The vulnerability can lead to unauthorized modifications in your application's dependencies, potentially compromising its security and functionality.

You should uninstall the social_crane_z3n package immediately and monitor your application for any unusual behavior.

Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall social_crane_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