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?

Remove requests-middleware 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is requests-middleware part of a known attack campaign?

Yes — requests-middleware is associated with the IN-MAL-2026-006974 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect requests-middleware in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking requests-middleware and packages like it before any post-install script runs.

Malicious package

requests-middlewarenpm

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

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

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-006974

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection