Which versions of @apiwizards/auth-middleware are malicious?

The following npm versions of @apiwizards/auth-middleware are flagged malicious: 4.7.0. Treat any of these as compromised.

How do I remediate @apiwizards/auth-middleware if I installed it?

Remove @apiwizards/auth-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 activity or persistence.

I already installed @apiwizards/auth-middleware — how do I know if it already compromised me?

If @apiwizards/auth-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 @apiwizards/auth-middleware part of a known attack campaign?

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

Malicious package

@apiwizards/auth-middlewarenpm

Malicious code in @apiwizards/auth-middleware (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6211

Immediate action

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

npm uninstall @apiwizards/auth-middleware

What this malware does

The package advertises itself as auth middleware but its main entry (index.js) is a 21KB obfuscator.io-packed file that, on require, performs a hidden download-and-execute pipeline. The single-file main uses an RC4-decoded 273-entry string array and control-flow flattening to conceal its require targets and network destination. On load it requires fs/os/path/child_process plus an HTTP client, installs no-op handlers for uncaughtException/unhandledRejection to suppress errors, constructs a host string via chained replaceAll calls on an obfuscated literal, performs an HTTP GET, writes the response body to disk with flag 'w+', and then invokes child_process.exec on the fetched bytes with windowsHide:true and cwd=process.cwd(). Any service that imports this package executes attacker-controlled remote code in its process context. The package.json has empty description and author and uses a generic name (@apiwizards/auth-middleware) consistent with namespace abuse targeting developers searching for an auth library.

Malicious versions

1 flagged

4.7.0

Indicators of compromise (SHA-256)

ba0f33946c3dd0624d21c0e99beb12f22b880bc126a3474753b38a9799fc5293

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

Campaign

IN-MAL-2026-007075

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @apiwizards/auth-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