Malicious Code Detected in @transaction-list/transaction-list-md Package

Summary

23/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-474: Malicious code in @transaction-list/transaction-list-md (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @transaction-list/transaction-list-md package is a Node.js library used for managing transaction lists in applications. It is designed to provide developers with an easy way to handle and display transaction data. However, this package has been identified as containing malicious code, posing a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the @transaction-list/transaction-list-md package. This code can potentially compromise the security of applications that depend on this package, leading to unauthorized access, data breaches, or other malicious activities. The package was flagged by Amazon Inspector, indicating a serious threat to users.

How To Fix

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

npm uninstall @transaction-list/transaction-list-md

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 immediate updating is not feasible, consider removing the @transaction-list/transaction-list-md package from your project until a secure version is released. You can do this by running: npm uninstall @transaction-list/transaction-list-md.

Conclusion

The discovery of malicious code in the @transaction-list/transaction-list-md package highlights the importance of maintaining secure dependencies in software development. By promptly addressing this vulnerability through updates and monitoring, developers can protect their applications from potential threats.

See every vulnerability recorded for @transaction-list/transaction-list-md →

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions within your application, potentially leading to data theft or system compromise.

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

Yes, you can remove the package from your project or replace it with a similar, secure alternative until a patched version is available.

It is recommended to regularly check for vulnerabilities, ideally after every major update or at least once a month.

If you suspect that your application has been compromised, immediately audit your code, remove the malicious package, and change any sensitive credentials.

How To Fix

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

npm uninstall @transaction-list/transaction-list-md

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