Which versions of requests-middleware are malicious?

The following npm versions of requests-middleware are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate requests-middleware if I installed it?

requests-middleware is a typosquat — you almost certainly intended a legitimately-named package. Remove requests-middleware, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed requests-middleware — how do I know if it already compromised me?

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

Yes — requests-middleware is associated with the IN-MAL-2026-006974, RLMA-2026-05606 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 requests-middleware 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 requests-middleware (version 1.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging requests-middleware across your stack and pipelines.

Malicious package

requests-middlewarenpm

requests-middleware is a confirmed malicious npm package (MAL-2026-6096) that typosquats a legitimate package to trick installs (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in requests-middleware (npm)

MAL-2026-6096

Immediate action

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

npm uninstall requests-middleware

What this malware does

The package masquerades as a typosquat of the legacy request/requests HTTP library, copying that project's README, dependencies, and source files verbatim, with a malicious dropper grafted on. Its sole exported function middleware (index.js:117-122) detached-spawns node lib/logger.js with { detached: true, stdio: 'ignore' } and immediately unref()s the child, so the loader runs silently and outlives the parent process. lib/logger.js then uses axios to GET https://www.jsonkeeper.com/b/YL7GN, extracts the JS payload from the response's Cookie field, and evaluates it with new Function.constructor('require', s)(require), retrying up to 5 times. This grants attacker-controlled JavaScript full require access in the consumer process. The remote URL is disguised in lib/logger.js:4-8 as DEV_API_KEY inside a fake process.env-shaped object to look like benign configuration. jsonkeeper.com is an anonymous, author-mutable paste host, so the executed bytes can change at any time without any package update. Any application that imports this package and invokes the default middleware export will execute remote attacker code.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

cfd9564690d64c44a730b088f4295c75b36e9d2fb164e2c7aa9ec2367153ada6

7862352bd49322fe4d5dbef4795a480db3f6db8e185bd5958373ef682485bcd7

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for requests-middleware (version 1.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging requests-middleware across your stack and pipelines.
If you installed it — respond
requests-middleware is a typosquat — you almost certainly intended a legitimately-named package. Remove requests-middleware, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If requests-middleware 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 requests-middleware 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. requests-middleware on npm has been identified as a malicious package (version 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006974RLMA-2026-05606

References

npmjs.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks requests-middleware-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