Which versions of security-env-loader are malicious?

The following npm versions of security-env-loader are flagged malicious: 3.11.0. Treat any of these as compromised.

How do I remediate security-env-loader if I installed it?

security-env-loader is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed security-env-loader — how do I know if it already compromised me?

If security-env-loader 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 security-env-loader part of a known attack campaign?

Yes — security-env-loader is associated with the IN-MAL-2026-003466, GHSA-rv4w-rvp6-p6rg 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 security-env-loader 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 security-env-loader (version 3.11.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging security-env-loader across your stack and pipelines.

Malicious package

security-env-loadernpm

Malicious code in security-env-loader (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4665

Immediate action

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

npm uninstall security-env-loader

What this malware does

Package impersonates the popular dotenv library (identical description and repo URL git://github.com/motdotla/dotenv.git) and exposes a matching config() API. When a consumer calls require('security-env-loader').config(...), lib/main.js loads lib/sync-safe-read.js — an obfuscator.io-packed module (rotated string array, _0x-style hex identifiers) that runs at top level. The module collects os.hostname(), os.type()/release()/arch(), MAC addresses from os.networkInterfaces(), and the entire process.env via JSON.stringify(process.env), then POSTs/GETs the data as query parameters to a base64-decoded URL (https://ip-core-api-0511.vercel.app/api; the same value is shipped in the package's.env as AUTH_API=aHR0cHM6Ly9pcC1jb3JlLWFwaS0wNTExLnZlcmNlbC5hcHAvYXBp). The exfiltration loop fires every 5 seconds via setInterval. The response from the C2 is parsed and when status==='log', message is passed to eval(), giving the operator persistent arbitrary-code execution in any host process that imports this package. Because the package's stated purpose is to load environment variables, the exfiltrated process.env is highly likely to contain live API keys, database credentials, and cloud tokens.

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.

Malicious versions

1 flagged

3.11.0

Indicators of compromise (SHA-256)

cf2b538ca6f5582ba25c054253f091eacca05571066d7237d6f693f23938e37c

55ddec70941f0321ec26a5e703be285db779bee6c717d6fb1a2e345b9c3d500c

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for security-env-loader (version 3.11.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging security-env-loader across your stack and pipelines.
If you installed it — respond
security-env-loader is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If security-env-loader 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 security-env-loader 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. security-env-loader on npm has been identified as a malicious package (version 3.11.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003466GHSA-rv4w-rvp6-p6rg

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks security-env-loader-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database