CVE-2022-3353: Malicious code in getectort (npm)

getectort Updated 02 Oct 2025

Summary

19/08/2022
CRITICAL
No i
Critical
Not published

MAL-2022-3353: Malicious code in getectort (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 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

getectort is an npm package that provides functionality for detecting and analyzing code in various programming languages. It is commonly used in software development projects to identify potential vulnerabilities and improve code quality. However, the package has been found to contain malicious code, which poses a significant security risk to any computer that has it installed or running.

Vulnerability Detail

The malicious code in getectort can compromise the security of the affected computer. It is advised to consider any computer with this package installed as fully compromised. This means that all secrets and keys stored on that 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, as full control of the computer may have been given to an outside entity.

How To Fix

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

npm uninstall getectort

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 mentioned for this vulnerability. However, it is crucial to follow the steps mentioned in the 'how_to_fix' section to mitigate the risk and ensure the security of the affected system.

Conclusion

The presence of malicious code in the getectort npm package poses a significant security risk to any computer that has it installed or running. It is crucial to take immediate action by rotating all secrets and keys, removing the package, and conducting a thorough security audit. Implementing additional security measures will help prevent future attacks. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for getectort →

Share this vulnerability

FAQ

getectort is an npm package used for detecting and analyzing code in various programming languages.

The malicious code in getectort can compromise the security of the affected computer, potentially giving full control to an outside entity. It is advised to rotate all secrets and keys stored on the computer and conduct a thorough security audit.

If you have getectort installed on your computer, it is recommended to rotate all secrets and keys stored on the computer from a different computer, remove the getectort package, and conduct a security audit to ensure the system's integrity.

Removing the getectort package may not guarantee the removal of all malicious software resulting from its installation. It is essential to conduct a thorough security audit to identify any potential unauthorized access or malicious activities.

To prevent future attacks, it is recommended to implement additional security measures such as firewall rules and intrusion detection systems. Regular security audits and updates to software dependencies are also crucial.

How To Fix

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

npm uninstall getectort

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