Malicious Code Vulnerability in concerned_swift_0xrequest Package

concerned_swift_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100812: Malicious code in concerned_swift_0xrequest (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 concerned_swift_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate interactions with the tea protocol, which incentivizes developers through token rewards. However, it has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the concerned_swift_0xrequest package. This code is designed to manipulate the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially harming developers' reputations and the integrity of the npm ecosystem.

How To Fix

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

npm uninstall concerned_swift_0xrequest

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

As a temporary measure, you can remove the concerned_swift_0xrequest package from your project by executing the following command: npm uninstall concerned_swift_0xrequest. This will prevent any malicious activity associated with the package until a secure version is available.

Conclusion

The concerned_swift_0xrequest package has been identified as containing malicious code that compromises the integrity of the npm ecosystem. It is crucial for developers to take immediate action by updating or uninstalling the package to mitigate potential risks.

See every vulnerability recorded for concerned_swift_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed for interactions with the tea protocol.

The malicious code modifies package.json files, removes private flags, and republishes variants to pollute the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

As a workaround, you can uninstall the concerned_swift_0xrequest package to prevent any malicious activity until a secure version is available.

For more details, you can reach out to Amazon Inspector at actran@amazon.com.

How To Fix

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

npm uninstall concerned_swift_0xrequest

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