Malicious code in developer-integrity1 (npm)

developer-integrity1 Updated 02 Oct 2025

Summary

03/06/2024
CRITICAL
No i
Critical
Not published

MAL-2024-1513: Malicious code in developer-integrity1 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The developer-integrity1 package is an npm package used for integrity checks in software development. It provides functionality to ensure the integrity and authenticity of code and dependencies. However, this package is vulnerable to a malicious code injection.

Vulnerability Detail

The developer-integrity1 package has been compromised with malicious code. Any computer that has this package installed or running should be considered fully compromised. This means that all secrets and keys stored on that computer may have been exposed to an outside entity. It is crucial to rotate all affected secrets and keys 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 developer-integrity1

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 essential to follow the steps mentioned in the 'how_to_fix' section to mitigate the risk.

Conclusion

The developer-integrity1 package has been compromised with malicious code, posing a severe risk to the integrity and security of affected computers. It is essential to follow the provided steps to mitigate the vulnerability and ensure the safety of sensitive information. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for developer-integrity1 →

Share this vulnerability

FAQ

The impact of this vulnerability is severe as it compromises the integrity and security of the affected computer. All secrets and keys stored on that computer may have been exposed to an outside entity.

If you have the developer-integrity1 package installed, your computer is potentially affected. It is recommended to perform a security audit and rotate all secrets and keys stored on that computer.

Removing the developer-integrity1 package is recommended, but it may not guarantee the removal of all malicious software resulting from its installation. It is crucial to rotate all affected secrets and keys as well.

Yes, the fix involves rotating all affected secrets and keys stored on the affected computer from a different, secure computer. Additionally, the developer-integrity1 package should be removed.

If you suspect your computer is compromised, it is crucial to disconnect it from the network immediately. Perform a security audit, rotate all secrets and keys, and seek professional assistance to ensure complete remediation.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall developer-integrity1

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