Malicious Code Detected in elf-stats-ember-workbench-742 Package

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192765: Malicious code in elf-stats-ember-workbench-742 (npm). Affects elf-stats-ember-workbench-742 versions 1.0.2. 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 elf-stats-ember-workbench-742 package is an npm library designed for managing and analyzing statistics in Ember applications. It provides developers with tools to enhance their applications' performance metrics. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the elf-stats-ember-workbench-742 package. This code can potentially compromise the security of applications using this package, leading to unauthorized access, data breaches, or other malicious activities. The specific technical details of the malicious code are not disclosed, but its presence in the package version 1.0.2 has been confirmed by security researchers from Amazon Inspector and ReversingLabs.

How To Fix

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

npm uninstall elf-stats-ember-workbench-742

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, you may consider removing the elf-stats-ember-workbench-742 package from your project until a secure version is released. You can do this by running: npm uninstall elf-stats-ember-workbench-742.

Conclusion

The elf-stats-ember-workbench-742 package has been identified as containing malicious code, which poses a serious threat to applications using it. It is essential to update or remove the package to mitigate potential risks. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for elf-stats-ember-workbench-742 →

Share this vulnerability

FAQ

It is an npm package used for managing statistics in Ember applications.

The specific details of the malicious code are not disclosed, but it poses significant security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities using your package-lock.json file. Visit Vulert Scanner to check your application without signing up.

Consider uninstalling the package as a temporary measure until a secure version is available.

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

How To Fix

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

npm uninstall elf-stats-ember-workbench-742

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