Malicious Code Injection in structural_silkworm_z3n Package

structural_silkworm_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109214: Malicious code in structural_silkworm_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The structural_silkworm_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the structural_silkworm_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, potentially affecting other packages and applications relying on npm.

How To Fix

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

npm uninstall structural_silkworm_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 workaround, you can manually remove the structural_silkworm_z3n package from your project by running the command: npm uninstall structural_silkworm_z3n. Additionally, consider using alternative packages that do not exhibit malicious behavior.

Conclusion

The structural_silkworm_z3n package contains malicious code that poses a significant risk to applications using it. Immediate action is required to remove the package and prevent further exploitation. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for structural_silkworm_z3n →

Share this vulnerability

FAQ

The structural_silkworm_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to automatically generate and publish derivative packages.

The malicious code modifies your package.json file, removes private flags, and continuously republishes variants, which can lead to security vulnerabilities and pollution of the npm registry.

You should uninstall the structural_silkworm_z3n package immediately and monitor for any updates or patches that may address this vulnerability.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can check your application for vulnerabilities without any signup at the Vulert playground.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated with the latest security advisories for the packages you use.

How To Fix

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

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