Malicious Code Injection in surrounding_newt_z3n Package

surrounding_newt_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-90812: Malicious code in surrounding_newt_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 surrounding_newt_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing derivative packages with altered metadata.

Vulnerability Detail

The vulnerability in the surrounding_newt_z3n package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to potential pollution of the npm registry and compromising the integrity of the packages available to developers.

How To Fix

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

npm uninstall surrounding_newt_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 may consider removing the surrounding_newt_z3n package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall surrounding_newt_z3n'. Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The surrounding_newt_z3n package is compromised by malicious code that alters package metadata for nefarious purposes. It is crucial to take immediate action by uninstalling the package and monitoring your project for any unauthorized changes. Stay informed about updates and consider using tools like Vulert for ongoing vulnerability management.

See every vulnerability recorded for surrounding_newt_z3n →

Share this vulnerability

FAQ

It is an npm package used for JavaScript development, but it has been identified as part of a malicious campaign.

The vulnerability can lead to unauthorized modifications in your package.json file and potentially compromise the integrity of your application.

You should uninstall the package immediately and monitor your project for any unauthorized changes.

Check for updates to the surrounding_newt_z3n package regularly, as a patched version may be released.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. Visit Vulert Scanner to check if your application is affected.

How To Fix

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

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