Malicious Code Detected in elf-stats-silvered-toolkit-914: A Critical Vulnerability

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192784: Malicious code in elf-stats-silvered-toolkit-914 (npm). Affects elf-stats-silvered-toolkit-914 versions 1.0.1 – 1.0.3. 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 elf-stats-silvered-toolkit-914 is an npm package designed for statistical analysis of ELF (Executable and Linkable Format) files. It provides various tools for developers to analyze and manipulate ELF binaries. However, this package has been compromised, containing malicious code that poses significant security risks to users and their applications.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the elf-stats-silvered-toolkit-914 package. This code can potentially lead to unauthorized access, data breaches, or system compromise. The malicious nature of the code was identified by security researchers from Amazon Inspector and ReversingLabs, highlighting the importance of scrutinizing third-party packages before integration into projects.

How To Fix

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

npm uninstall elf-stats-silvered-toolkit-914

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 removing the elf-stats-silvered-toolkit-914 package from your project until a secure version is released. You can do this by running: npm uninstall elf-stats-silvered-toolkit-914.

Conclusion

The elf-stats-silvered-toolkit-914 package has been identified as containing malicious code, posing significant risks to users. It is crucial to update or remove the package to safeguard your applications. Utilize tools like Vulert to monitor for vulnerabilities in your software.

See every vulnerability recorded for elf-stats-silvered-toolkit-914 →

Share this vulnerability

FAQ

It is an npm package used for statistical analysis of ELF files, but it has been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities using your package-lock.json file. Check your application at Vulert Scanner.

Immediately uninstall the package and check for any updates or patches that may be released.

The vulnerability was discovered by security researchers from Amazon Inspector and ReversingLabs.

The risks include unauthorized access, data breaches, and potential system compromise due to the malicious code.

How To Fix

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

npm uninstall elf-stats-silvered-toolkit-914

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