Which versions of mongoose_update are malicious?

Every published version of mongoose_update on npm is considered malicious. Remove the package entirely.

How do I remediate mongoose_update if I installed it?

Remove mongoose_update from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed mongoose_update — how do I know if it already compromised me?

If mongoose_update 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.

Is mongoose_update part of a known attack campaign?

Yes — mongoose_update is associated with the GHSA-g9f3-5423-w9c8 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find mongoose_update across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mongoose_update (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mongoose_update across your stack and pipelines.

Malicious package

mongoose_updatenpm

Malicious code in mongoose_update (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-711

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall mongoose_update

What this malware does

The package mongoose_update was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

c8c705834895c7083b2f00f874d9761f360f0208ee61aaeec6af5c2a806841e5

91df51d75c82831870e737a45d083f0f75a4efd3fa5446b0c07a5c8c9ad910fd

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mongoose_update (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mongoose_update across your stack and pipelines.
If you installed it — respond
Remove mongoose_update from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If mongoose_update 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 mongoose_update 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

No. mongoose_update on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-g9f3-5423-w9c8

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mongoose_update-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring