Malicious Package in s3asy - GHSA-3wjm-33mw-h388

s3asy Updated 02 Oct 2025

Summary

01/09/2020
CRITICAL
No i
Critical
Not published

GHSA-3wjm-33mw-h388: Malicious Package in s3asy. Affects s3asy versions 0.4.8. 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

s3asy is an npm package that provides functionality for interacting with Amazon S3. It allows users to easily upload, download, and manage files in an S3 bucket. Version 0.4.8 of s3asy contained a malicious code that posed a security risk to applications using this version. The code, when executed in the browser, would extract sensitive information such as passwords, cvc, and card numbers from forms and send them to a remote server.

Vulnerability Detail

The vulnerability in s3asy version 0.4.8 allowed an attacker to collect sensitive user data by intercepting form submissions. This could lead to unauthorized access to user accounts, financial fraud, and privacy breaches. The malicious code was designed to specifically target password, cvc, and card number fields in forms. It would then send the extracted data to a remote server controlled by the attacker. This vulnerability could have severe consequences for applications using this version of s3asy.

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. The best course of action is to follow the recommended steps to fix the vulnerability by replacing the affected version of s3asy.

Conclusion

The presence of malicious code in version 0.4.8 of s3asy poses a critical security risk to applications using this version. It is crucial to replace this version with a secure alternative and evaluate the application for any potential data compromise. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for s3asy →

Share this vulnerability

FAQ

s3asy is an npm package that provides functionality for interacting with Amazon S3. It simplifies the process of managing files in an S3 bucket.

The malicious code in version 0.4.8 of s3asy allowed an attacker to extract sensitive user data, including passwords, cvc, and card numbers, from forms and send them to a remote server.

To fix this vulnerability, you should replace version 0.4.8 of s3asy with a version before or after 0.4.8. Additionally, evaluate your application to check if any user data was compromised.

There is no specific workaround mentioned for this vulnerability. It is recommended to follow the steps to fix the vulnerability by replacing the affected version of s3asy.

Version 0.4.7 of s3asy is considered safe and can be used as an alternative to version 0.4.8 to mitigate the vulnerability.

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