Which versions of ultimates-express are malicious?

The following npm versions of ultimates-express are flagged malicious: 3.7.7. Treat any of these as compromised.

How do I remediate ultimates-express if I installed it?

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

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

Yes — ultimates-express is associated with the GHSA-mgfx-pg8p-7m76, RLMA-2026-01632 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 ultimates-express 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 ultimates-express (version 3.7.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ultimates-express across your stack and pipelines.

Malicious package

ultimates-expressnpm

Malicious code in ultimates-express (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1012

Immediate action

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

npm uninstall ultimates-express

What this malware does

The package ultimates-express 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

3.7.7

Indicators of compromise (SHA-256)

326ff54f5c5a3a6434eab535ec03bbd32cc2b2136eaa9e7870a6444854b7872d

199dbb458ff55c6d08022e6326014d56aceb99ef7748d6e898a6faac9bff201b

f5cf8bbf93218741c5f748a4c0453663703fa8e47e920754a7d54c960dd5836b

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

Campaign

GHSA-mgfx-pg8p-7m76RLMA-2026-01632

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ultimates-express-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