Malicious Code Detected in geodynamo-standard-meteor-string Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21343: Malicious code in geodynamo-standard-meteor-string (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 geodynamo-standard-meteor-string package is an npm library designed for string manipulation within Meteor applications. It is utilized by developers to enhance the functionality of their applications with various string-related features. However, this package has been identified to contain malicious code, posing a significant risk to users who integrate it into their projects.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the geodynamo-standard-meteor-string package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other malicious activities. The issue affects all versions of the package starting from version 0, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall geodynamo-standard-meteor-string

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, developers can replace the functionality provided by the geodynamo-standard-meteor-string package with alternative libraries that offer similar string manipulation features without the associated risks.

Conclusion

The geodynamo-standard-meteor-string package has been identified as containing malicious code, which poses a serious risk to applications that utilize it. Users are advised to remove the package and seek alternatives until a secure version is released. Monitoring tools like Vulert can assist in identifying vulnerabilities in your projects.

See every vulnerability recorded for geodynamo-standard-meteor-string →

Share this vulnerability

FAQ

It is an npm library used for string manipulation in Meteor applications.

The specific nature of the malicious code has not been disclosed, but it poses security risks to applications using the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Remove the geodynamo-standard-meteor-string package immediately and consider using alternative libraries for string manipulation.

Currently, there is no patched version available. Users should monitor the package repository for any updates.

How To Fix

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

npm uninstall geodynamo-standard-meteor-string

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