Malicious Code Detected in frmtst Package - Security Alert

frmtst Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20963: Malicious code in frmtst (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The frmtst package is a Node.js library designed to facilitate formatting tasks within JavaScript applications. It is commonly used for its simplicity and effectiveness in managing string manipulations. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the frmtst package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall frmtst

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, consider using alternative packages that offer similar functionality without the associated risks. For example, you can explore packages like 'string-format' or 'lodash' for string manipulation tasks.

Conclusion

The frmtst package has been flagged for containing malicious code, posing a serious threat to applications that utilize it. Users are advised to remove the package and consider alternatives until a secure version is released. Staying informed and using tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for frmtst →

Share this vulnerability

FAQ

The frmtst package is used for formatting tasks in JavaScript applications, particularly for string manipulations.

The malicious code was identified by security researchers from Amazon Inspector, who conducted a thorough analysis of the package.

If you have used the frmtst package, it is crucial to remove it from your project immediately and consider using alternative packages.

Currently, there is no patched version available for the frmtst package. Users should monitor updates from the package maintainers for any future fixes.

You can use tools like Vulert, which monitors your package-lock.json file for real-time alerts on open-source vulnerabilities without requiring code access or installation.

How To Fix

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

npm uninstall frmtst

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