Which versions of fileupload-util are malicious?

The following npm versions of fileupload-util are flagged malicious: 2.4.3. Treat any of these as compromised.

How do I remediate fileupload-util if I installed it?

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

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

Yes — fileupload-util is associated with the GHSA-jmrr-h39h-r9g2, RLMA-2026-01320 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 fileupload-util 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 fileupload-util (version 2.4.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fileupload-util across your stack and pipelines.

Malicious package

fileupload-utilnpm

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

MAL-2026-690

Immediate action

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

npm uninstall fileupload-util

What this malware does

The package fileupload-util 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

2.4.3

Indicators of compromise (SHA-256)

86e2a72f365ef548c52ca11a5bcfa8cbca1b7ff90e2e35aa34b8d9c2abb9c854

284fb08fce78b3881a87fa045e3cd78babfd4be9859ffd8be916952b1088fc19

3c0bdac10bac0fa743b0a35158637860e6001776d990262d34a9cf44d1510b9d

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

Campaign

GHSA-jmrr-h39h-r9g2RLMA-2026-01320

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks fileupload-util-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