Malicious code in get-twitter-status (npm)

get-twitter-status Updated 02 Oct 2025

Summary

30/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8645: Malicious code in get-twitter-status (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 get-twitter-status package is an npm package that allows users to retrieve the status of a Twitter account. It is commonly used in applications that require fetching and displaying Twitter statuses. However, the package has been found to contain malicious code, compromising the security of any computer that has it installed or running.

Vulnerability Detail

The malicious code in the get-twitter-status package poses a significant security risk. Any computer with the package installed should be considered fully compromised. This means that all secrets and keys stored on that computer should be rotated immediately from a different computer. Simply removing the package may not guarantee the removal of all malicious software installed as a result of it. The package has been flagged as malware, and caution should be exercised to prevent further damage.

How To Fix

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

npm uninstall get-twitter-status

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 outlined in the 'how_to_fix' section to mitigate the risk and ensure the security of the affected computer.

Conclusion

The get-twitter-status package has been found to contain malicious code, compromising the security of any computer with it installed. To mitigate the risk, it is essential to rotate all secrets and keys, remove the package, and conduct a thorough security audit. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for get-twitter-status →

Share this vulnerability

FAQ

The get-twitter-status package is an npm package used to retrieve the status of a Twitter account.

The malicious code in the get-twitter-status package gives full control of the computer to an outside entity, potentially allowing access to sensitive information and enabling further malicious activities.

If you have the get-twitter-status package installed, it is crucial to rotate all secrets and keys stored on the affected computer from a different, secure computer. Additionally, remove the package and conduct a thorough security audit to identify any other potential compromises.

While removing the get-twitter-status package is recommended, there is no guarantee that it will remove all malicious software resulting from its installation. A thorough security audit is necessary to ensure the complete removal of any potential compromises.

To prevent further damage, it is crucial to follow the steps outlined in the 'how_to_fix' section. Additionally, conducting a security audit and implementing robust security measures can help mitigate the risk of future compromises.

How To Fix

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

npm uninstall get-twitter-status

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