Which versions of mockupnul are malicious?

The following npm versions of mockupnul are flagged malicious: 7.8.1. Treat any of these as compromised.

How do I remediate mockupnul if I installed it?

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

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

Yes — mockupnul is associated with the GHSA-7wv9-823h-6764, RLMA-2025-05060, RLUA-2026-01431 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 mockupnul 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 mockupnul (version 7.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mockupnul across your stack and pipelines.

Malicious package

mockupnulnpm

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

Malicious code in mockupnul (npm)

MAL-2025-47077

Immediate action

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

npm uninstall mockupnul

What this malware does

The package mockupnul 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

1 flagged

7.8.1

Indicators of compromise (SHA-256)

8b4708b8e8ad3a0cbe662813ec6e76bb95f4125dc77a98dc1c39f4c5ae95321b

6f45a81d96fc6bf4c099902485c7bb4b3ca5bbf71ba34316193e86a8f79fe86a

86a1f24053b1bc0e7c81a833a76af517394acdf6b759543724df5d9bfbe436d3

6c0bdd438b392187633ee9293439fe056192dedfdf125fbaf3264f3b63c15ce5

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

Campaign

GHSA-7wv9-823h-6764RLMA-2025-05060RLUA-2026-01431

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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