Malicious Code Injection in memories-core-web Package

memories-core-web Updated 21 Oct 2026

Summary

20/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-18106: Malicious code in memories-core-web (npm). Affects memories-core-web versions 99.0.0. 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 memories-core-web package is an npm library designed for web applications, providing essential functionalities for managing user interactions and data. However, it has been found to contain a significant vulnerability that allows malicious code execution during the installation process, posing a serious risk to users and their systems.

Vulnerability Detail

The vulnerability originates from a preinstall lifecycle script defined in the package.json file of memories-core-web. This script executes a curl command that sends sensitive information, including the installer's hostname and username, to a hardcoded URL on webhook.site. This action occurs automatically during the npm install process, leading to unauthorized data transmission to a third-party collector, which is not associated with the package's publisher. The implications of this vulnerability include potential exposure of sensitive user data and compromise of system integrity.

How To Fix

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

npm uninstall memories-core-web

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, users can manually remove the preinstall script from the package.json file before running npm install. This can be done by editing the package.json file and deleting the line that includes the preinstall script.

Conclusion

The memories-core-web package contains a serious vulnerability that allows for the transmission of sensitive user data to an external server during installation. Users are advised to update the package to a patched version and consider workarounds to mitigate risks until an update can be applied.

See every vulnerability recorded for memories-core-web →

Share this vulnerability

FAQ

The vulnerability involves a malicious preinstall script that sends sensitive user information to an external server during installation.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without needing to sign up.

The risks include unauthorized access to sensitive user information and potential compromise of the user's system.

Users should check for a patched version of the memories-core-web package and update it accordingly to mitigate the vulnerability.

If immediate updates are not possible, consider removing the preinstall script from the package.json file as a temporary workaround.

How To Fix

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

npm uninstall memories-core-web

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