CVE-2022-593: Malicious code in @slashkit/core (npm)

@slashkit/core Updated 02 Oct 2025

Summary

20/06/2022
CRITICAL
No i
Critical
Not published

MAL-2022-593: Malicious code in @slashkit/core (npm). Affected versions are not published. 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 @slashkit/core package is an npm package that provides core functionality for the Slashkit framework. It is used to build web applications and APIs. The package is widely used in various projects and has a large user base. However, it has been discovered that the package contains malicious code, which poses a significant security risk to any computer that has it installed or running.

Vulnerability Detail

The malicious code in @slashkit/core has been identified as a serious security threat. Any computer with this package installed or running should be considered fully compromised. The code has the potential to give full control of the computer to an outside entity, allowing them to access and manipulate sensitive information, such as secrets and keys. It is crucial to rotate all affected secrets and keys immediately from a different computer. Removing the package may not guarantee the removal of all malicious software resulting from its installation.

How To Fix

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

npm uninstall @slashkit/core

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

There is no specific workaround available for this vulnerability. It is essential to follow the recommended steps for fixing the issue.

Conclusion

The presence of malicious code in the @slashkit/core package poses a severe security risk to any computer that has it installed or running. It is essential to take immediate action by rotating affected secrets and keys, removing the package, and conducting a thorough security audit. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for @slashkit/core →

Share this vulnerability

FAQ

@slashkit/core is an npm package that provides core functionality for the Slashkit framework. It is used to build web applications and APIs.

The malicious code in @slashkit/core can compromise your computer by giving full control to an outside entity. This can lead to unauthorized access to sensitive information and potential manipulation of your system.

If you have the @slashkit/core package installed, it is crucial to rotate all secrets and keys stored on your computer from a different machine. Additionally, remove the package from your system and conduct a security audit to ensure no other malicious software is present.

While removing the @slashkit/core package is recommended, it may not guarantee the removal of all malicious software resulting from its installation. It is essential to conduct a thorough security audit to ensure your system is clean.

To prevent this vulnerability in the future, it is crucial to regularly update your packages and dependencies. Stay informed about security advisories and promptly apply any necessary patches or updates.

How To Fix

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

npm uninstall @slashkit/core

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