# MAL-2026-14484: Malicious code in react-remove-properties (npm)


- **Type:** Malicious package
- **Package:** `react-remove-properties` (npm)
- **Published:** 25 Aug 2026
- **Also known as:** GHSA-m8m4-9m7c-742j

## What is MAL-2026-14484?

MAL-2026-14484 is a malicious package in react-remove-properties, published on 25 Aug 2026. 

### Official description

package.json declares the package's own name in both dependencies and devDependencies pointing at http://pack.nppacks.com/npm/react-remove-properties — a plain-HTTP, non-npm-registry, unpinned URL. On `npm install`, npm fetches and installs whatever tarball is served at that mutable third-party endpoint into the installer's node_modules, giving the operator of pack.nppacks.com arbitrary-code delivery into the install. The source is not the official registry, the transport is cleartext HTTP (trivially MITM-able on any network path), the resolution is unpinned (no integrity/hash), and the host is outside npm's audit surface. A header comment in index.js labels the package as 'Security Research Testing Purpose,' but a self-label does not change the delivery mechanism.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

## What should I do about MAL-2026-14484?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-14484 is a malicious package: react-remove-properties (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-14484/ (Markdown: https://insights.sbomify.com/MAL-2026-14484/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-14484

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-14484/
Summaries are generated and may contain mistakes; the official description above is the record.