Which versions of fileupload-core are malicious?

The following npm versions of fileupload-core are flagged malicious: 0.0.1-security, 2.4.3. Treat any of these as compromised.

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

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

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

Yes — fileupload-core is associated with the GHSA-jmrw-v7rp-6m4v, RLMA-2026-01319 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-core 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-core (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fileupload-core across your stack and pipelines.

Malicious package

fileupload-corenpm

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

MAL-2026-529

Immediate action

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

npm uninstall fileupload-core

What this malware does

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

2 flagged

0.0.1-security2.4.3

Indicators of compromise (SHA-256)

aa58dfc19074922a9db4713e1aa1c17edc8de5a937d01a5c08271d4940bcc388

5cfeee070d9e37cd2dda0d7557f93098e1589be17d77ff38abf265f564574ca3

37bc24255dd6119eea6a3b3b48a5459094f24bfc69136784b770e1f7707d5834

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

Campaign

GHSA-jmrw-v7rp-6m4vRLMA-2026-01319

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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