Malicious Package in scroool

scroool Updated 02 Oct 2025

Summary

11/09/2020
CRITICAL
No i
Critical
Not published

GHSA-p7w2-mc6m-mfx2: Malicious Package in scroool. Affects scroool versions 0.1.7. 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 scroool package is an npm package that provides functionality for scrolling elements on web pages. It is commonly used in web development projects to enhance user experience by enabling smooth scrolling. However, version 0.1.7 of scroool contained malicious code that posed a serious security risk to applications utilizing this version.

Vulnerability Detail

The vulnerability in version 0.1.7 of scroool involved the inclusion of malicious code. When executed in the browser, this code would extract sensitive information such as passwords, cvc, and card numbers from forms and send them to a remote server. The extracted data was then potentially used for malicious purposes. This vulnerability could lead to the compromise of user data and pose a significant threat to the security and privacy of affected applications.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. However, users can mitigate the risk by removing version 0.1.7 of scroool and implementing additional security measures such as input validation and encryption to protect sensitive user data.

Conclusion

The presence of malicious code in version 0.1.7 of the scroool package poses a critical security risk to applications utilizing this version. It is crucial to remove this version, evaluate for any compromised user data, and consider downgrading to version 0.1.6 as a temporary solution. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for scroool →

Share this vulnerability

FAQ

This vulnerability can lead to the compromise of user data, including passwords and credit card information, which can be used for malicious purposes.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.

If your application is affected, it is recommended to remove version 0.1.7 of scroool and evaluate your application for any compromised user data. Consider downgrading to version 0.1.6 as a temporary solution.

There are no specific known exploits mentioned for this vulnerability. However, the malicious code in version 0.1.7 of scroool could potentially be used to extract sensitive information from affected applications.

To prevent similar vulnerabilities, it is essential to regularly update your packages to the latest secure versions. Additionally, ensure that you only use trusted and well-maintained packages from reputable sources.

How To Fix

No fixed version is published for this vulnerability.

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