Critical Malicious Code Vulnerability in tkacg3 Package

tkacg3 Updated 19 Oct 2026

Summary

19/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-18037: Malicious code in tkacg3 (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 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

The tkacg3 package is an npm module that is utilized for various functionalities in JavaScript applications. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to developers and organizations relying on this package for their projects.

Vulnerability Detail

The tkacg3 package has been flagged for containing embedded malicious code, which can lead to full compromise of any computer running it. This vulnerability originated from a malicious actor who injected harmful code into the package, allowing unauthorized access to sensitive information such as secrets and keys stored on the affected system. The ramifications of this vulnerability are severe, as it can lead to data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall tkacg3

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 are no effective workarounds for this vulnerability other than removing the tkacg3 package and securing your system. Ensure that you monitor your system for any signs of compromise after removal.

Conclusion

The tkacg3 package has been identified as a significant security risk due to the presence of malicious code. Immediate action is required to remove the package and secure any compromised systems. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.

See every vulnerability recorded for tkacg3 →

Share this vulnerability

FAQ

You should immediately uninstall the tkacg3 package using the command 'npm uninstall tkacg3' and rotate any sensitive information stored on the affected system.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Failing to remove tkacg3 can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.

While many npm packages are safe, it is essential to vet packages before installation and keep an eye on vulnerability reports to ensure the security of your applications.

How To Fix

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

npm uninstall tkacg3

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