Malicious Code Injection in concrete_galliform_requirement Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93710: Malicious code in concrete_galliform_requirement (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The concrete_galliform_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. It is designed to facilitate the development process by allowing developers to include libraries and tools easily. However, this package has been identified as part of a malicious campaign that exploits npm's publishing system, leading to significant security risks for users.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the concrete_galliform_requirement package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished to the npm registry. This behavior not only inflates developer reputation scores for the tea protocol token rewards but also pollutes the npm ecosystem, potentially leading to further exploitation and security breaches.

How To Fix

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

npm uninstall concrete_galliform_requirement

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 workaround, you can avoid using the concrete_galliform_requirement package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The concrete_galliform_requirement package poses a significant security risk due to its malicious code that modifies essential files and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert to ensure the integrity and security of their applications.

See every vulnerability recorded for concrete_galliform_requirement →

Share this vulnerability

FAQ

It is an npm package used for managing dependencies in JavaScript applications, but it has been identified as malicious.

The vulnerability can lead to unauthorized modifications of your package.json file and may expose your application to further security risks.

You should uninstall the concrete_galliform_requirement package immediately and check for any alternative packages.

You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall concrete_galliform_requirement

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