Malicious Code in tkn-poc (npm)

tkn-poc Updated 02 Oct 2025

Summary

09/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8495: Malicious code in tkn-poc (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 tkn-poc package is an npm package that is used for [provide brief description of package functionality]. It is vulnerable to a malicious code injection that can compromise the security of any computer on which it is installed or running. This vulnerability has been identified in the package and immediate action is required to mitigate the potential risks.

Vulnerability Detail

The tkn-poc package contains a malicious code that has been identified as ghsa-malware (a3230b2e14e4f5e50ae022fdb7a081a52260e3c68f1a4b50add1dcca4afdc1a5). This code compromises the security of the computer on which the package is installed, giving full control to an outside entity. As a result, all secrets and keys stored on the affected computer should be rotated 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 tkn-poc

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 known workaround for this vulnerability. It is crucial to follow the steps mentioned in the 'how_to_fix' section to mitigate the risks.

Conclusion

The tkn-poc package has been identified as containing malicious code that compromises the security of the affected computer. Immediate action is required to rotate all secrets and keys stored on the computer, remove the package, and run a thorough security scan. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for tkn-poc →

Share this vulnerability

FAQ

tkn-poc is an npm package used for [provide brief description of package functionality].

The malicious code in tkn-poc, identified as ghsa-malware (a3230b2e14e4f5e50ae022fdb7a081a52260e3c68f1a4b50add1dcca4afdc1a5), gives full control of the affected computer to an outside entity. This compromises the security of the computer and puts all stored secrets and keys at risk.

If you have tkn-poc installed, it is recommended to immediately rotate all secrets and keys stored on the affected computer from a different computer. Remove the tkn-poc package and run a thorough security scan to ensure the removal of any remaining malicious software.

While removing the tkn-poc package is recommended, it may not guarantee the removal of all malicious software resulting from its installation. It is important to run a thorough security scan to identify and remove any remaining malicious software.

After removing tkn-poc, it is crucial to run a thorough security scan on the affected computer to identify and remove any remaining malicious software. Additionally, it is recommended to regularly update and patch all software and use reliable security measures to protect against future vulnerabilities.

How To Fix

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

npm uninstall tkn-poc

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