Which versions of modules9382 are malicious?

The following npm versions of modules9382 are flagged malicious: 22.26.51. Treat any of these as compromised.

How do I remediate modules9382 if I installed it?

Remove modules9382 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 modules9382 — how do I know if it already compromised me?

If modules9382 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 modules9382 part of a known attack campaign?

Yes — modules9382 is associated with the GHSA-2v4r-jvvg-9799, RLMA-2025-03932, RLUA-2026-01433 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 modules9382 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 modules9382 (version 22.26.51). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging modules9382 across your stack and pipelines.

Malicious package

modules9382npm

modules9382 is a confirmed malicious npm package (MAL-2025-5708) that executes malicious code on install (malicious version 22.26.51). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in modules9382 (npm)

MAL-2025-5708

Immediate action

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

npm uninstall modules9382

What this malware does

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

1 flagged

22.26.51

Indicators of compromise (SHA-256)

65a087c59c3c0f929ea8866c114728420dfd67459abc44b2ea2830382108127e

a4c912e0a09402474cf70d4a6de0eb253845bda9c60f9d7a4e287e8a17627627

ce59ecd68efab0f8dddfeb6f3571253605c76b0ec106a294339b2cd9e8c642f3

12b3fb2a0905c224226c2e8e3001f2dffcd41a7e72414b946d5c4d5661087ebc

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 modules9382 (version 22.26.51). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging modules9382 across your stack and pipelines.
If you installed it — respond
Remove modules9382 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 modules9382 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 modules9382 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. modules9382 on npm has been identified as a malicious package (version 22.26.51 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2v4r-jvvg-9799RLMA-2025-03932RLUA-2026-01433

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks modules9382-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

Explore

All malware advisories How O3 detects malware Vulnerability database