Malicious Code Injection in semantic_aphid_z3n Package

semantic_aphid_z3n Updated 25 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-130094: Malicious code in semantic_aphid_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 semantic_aphid_z3n package is part of the npm ecosystem, often used in JavaScript projects. It is associated with the tea.xyz token reward campaign, which has been linked to numerous malicious packages flooding the npm registry. This package is designed to manipulate package metadata and publish derivative packages, potentially compromising the integrity of projects that depend on it.

Vulnerability Detail

The vulnerability in the semantic_aphid_z3n package stems from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only inflates developer reputation scores for token rewards but also poses a risk of dependency confusion and potential exploitation in projects relying on this package.

How To Fix

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

npm uninstall semantic_aphid_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 semantic_aphid_z3n package and replace it with a trusted alternative. Additionally, you can use the following command to uninstall the package: npm uninstall semantic_aphid_z3n.

Conclusion

The semantic_aphid_z3n package contains malicious code that poses a significant risk to projects using it. Immediate action is required to remove this package and monitor for any updates. Utilizing tools like Vulert can help in identifying and managing vulnerabilities effectively.

See every vulnerability recorded for semantic_aphid_z3n →

Share this vulnerability

FAQ

The semantic_aphid_z3n package is an npm package associated with the tea.xyz token reward campaign, often containing malicious code designed to manipulate package metadata.

This vulnerability can compromise the integrity of your project by introducing malicious code that alters package metadata and can lead to dependency confusion.

You should immediately remove the semantic_aphid_z3n package from your project and monitor for any updates or patches that may address the vulnerability.

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

To prevent future vulnerabilities, regularly audit your dependencies, use trusted packages, and consider employing automated tools that monitor for vulnerabilities.

How To Fix

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

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