Which versions of express-rate-controller are malicious?

The following npm versions of express-rate-controller are flagged malicious: 2.0.0, 2.0.1. Treat any of these as compromised.

How do I remediate express-rate-controller if I installed it?

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

If express-rate-controller was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is express-rate-controller part of a known attack campaign?

Yes — express-rate-controller is associated with the IN-MAL-2026-014871, IN-MAL-2026-015880 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 express-rate-controller across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for express-rate-controller (2 malicious versions).

Malicious package

express-rate-controllernpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

express-rate-controller is a confirmed malicious npm package (MAL-2026-12378) that executes malicious code on install (malicious versions 2.0.0, 2.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in express-rate-controller (npm)

MAL-2026-12378

Immediate action

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

npm uninstall express-rate-controller

What this malware does

The package is published under the name express-rate-controller but describes itself as an SVG utilities library and ships a bin named svgcraft — the name, description, and CLI do not match. src/index.cjs exports getPlugin(), which issues an HTTPS GET to https://api.avax-test.dev/ext/bc/rpc with TLS verification disabled (rejectUnauthorized: false) and passes the response body to new Function('require', data)(require), executing whatever JavaScript that endpoint returns with full require access. The loader is present only in the CommonJS build; index.mjs and index.d.ts do not declare getPlugin(), hiding the export from typed and ESM consumers. Any consumer that require()s the package and invokes getPlugin() — or downstream code that iterates the exported api object — runs attacker-controlled code delivered from api.avax-test.dev.

Malicious versions

2 flagged

2.0.02.0.1

Indicators of compromise (SHA-256)

43c2ed4e91378e1ca9df444de58c0ff3afebce39741ab67011b55490740cac11

0f8f55db832d152ae267d8eecd35e28ad2fe646aa93011d3e6f30161a1d9f18f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for express-rate-controller (2 malicious versions).
If you installed it — respond
Remove express-rate-controller 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 express-rate-controller was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. express-rate-controller on npm has been identified as a malicious package (versions 2.0.0, 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014871IN-MAL-2026-015880

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks express-rate-controller-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