# MAL-2026-5929: Malicious code in backoffice-charges-module (npm)


- **Type:** Malicious package
- **Package:** `backoffice-charges-module` (npm)
- **Published:** 16 Jun 2026
- **Also known as:** GHSA-mmhq-hrgp-xjhx

## What is MAL-2026-5929?

MAL-2026-5929 is a malicious package in backoffice-charges-module, published on 16 Jun 2026. 

### Official description

On every `npm install`, the `preinstall` lifecycle script (`node index.js > /dev/null 2>&1`) silently HTTPS-POSTs a JSON payload to `https://avamnrwqo7.rbmock.dev/` containing the package name, a generated execution_id, `process.version`, `process.platform`, `process.arch`, and an ISO timestamp. Output is redirected to /dev/null to hide the network call from the installer. The package has empty description, author 'poc', declares a `main.js` that is not shipped, and uses an artificially high version number (1.999.0) — classic dependency-confusion/typosquat reconnaissance signals. The beacon allows whoever controls `avamnrwqo7.rbmock.dev` to enumerate which internal CI runners and developer hosts have resolved this name from the public registry instead of an internal one, identifying targets for follow-up payloads.

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-5929?

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-5929 is a malicious package: backoffice-charges-module (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-5929/ (Markdown: https://insights.sbomify.com/MAL-2026-5929/index.md)
```

## Sources

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

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