backoffice-charges-modulenpm
backoffice-charges-module is a confirmed malicious npm package (MAL-2026-5929) that opens a backdoor for remote access (malicious versions 1.999.0, 2.999.0, 2.999.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in backoffice-charges-module (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for backoffice-charges-module (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging backoffice-charges-module across your stack and pipelines.
If you installed it — respond
backoffice-charges-module establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If backoffice-charges-module was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks backoffice-charges-module before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks backoffice-charges-module-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.