Malicious Code Detected in terrain-sample Package - npm Vulnerability

terrain-sample Updated 01 Dec 2025

Summary

01/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191529: Malicious code in terrain-sample (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 terrain-sample package is an npm library designed for developers to create and manage terrain-related functionalities in their applications. It is commonly used in projects that require geographical data manipulation and visualization. However, recent findings have revealed that this package contains malicious code, posing significant risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability originates from the terrain-sample package, which has been identified to contain malicious code. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other harmful consequences. The malicious nature of this code was confirmed by Amazon Inspector, which flagged the package for its harmful behavior.

How To Fix

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

npm uninstall terrain-sample

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

If updating the package is not feasible, consider removing the terrain-sample package from your project until a secure version is released. You can do this by executing: npm uninstall terrain-sample.

Conclusion

The terrain-sample package has been identified as containing malicious code, posing significant risks to applications that use it. Users are urged to update or remove the package to safeguard their projects. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for terrain-sample →

Share this vulnerability

FAQ

The terrain-sample package is an npm library used for managing terrain-related functionalities in applications, often for geographical data manipulation.

The malicious code was detected by Amazon Inspector, which flagged the terrain-sample package for containing harmful code.

Using the terrain-sample package can lead to unauthorized access, data breaches, and other security vulnerabilities in your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner without needing to sign up.

If you cannot update the terrain-sample package, it is advisable to uninstall it from your project until a secure version is available.

How To Fix

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

npm uninstall terrain-sample

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