Which versions of secdriven are malicious?

The following npm versions of secdriven are flagged malicious: 1.0.1, 1.0.7, 1.0.8. Treat any of these as compromised.

How do I remediate secdriven if I installed it?

secdriven 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 secdriven — how do I know if it already compromised me?

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

Yes — secdriven is associated with the IN-MAL-2026-004294, IN-MAL-2026-004293, IN-MAL-2026-004291, IN-MAL-2026-004292 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 secdriven 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 secdriven (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging secdriven across your stack and pipelines.

Malicious package

secdrivennpm

Malicious code in secdriven (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4263

Immediate action

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

npm uninstall secdriven

What this malware does

On npm install, postinstall.js executes whoami via child_process and reads os.hostname(), os.platform(), the working directory, and CI / GITHUB_REPOSITORY environment variables, then transmits them as query-string parameters in an HTTPS GET to a hardcoded interactsh subdomain (lg5ys3jebfzwk366pilidbmah1nsbszh.oastify.com) under the path /google/secdriven/. A DNS lookup using whoami output as a subdomain provides a fallback exfiltration channel. The package description ("Security research canary — Google") and README pointing at a Google CTF internal package.json indicate this is a dependency-confusion payload targeting Google's internal namespace; any installer whose resolver picks up this public name leaks host identity, username, working directory, and CI repository path to the third-party OOB-detection endpoint without consent. Whether published as research or attack, the installer-side effect is the same: unconsented identity-and-environment beacon at install time.

The OpenSSF Package Analysis project identified 'secdriven' @ 1.0.8 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged

1.0.11.0.71.0.8

Indicators of compromise (SHA-256)

bafef125d75ec1f8f8b4d9c19e43da29dc8efccecdab347c19a74d1602433535

5accf0a7d5ef749122c408d1b78a4585c663d7218ea42bd276d6e0b14ef04e1b

5f9fc2c83fd07e30cba7137fce3d4701f5bc1feb9146c396ae939f3acb720643

975aa97eecdefbe83b5eab461ef8abe6850de825ce44496cbb351908bc0d51ec

e64bd0b65a5cddc6e2032cfdd0a23f06c980a25066490b223d07e1b2e4efe3d8

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 secdriven (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging secdriven across your stack and pipelines.
If you installed it — respond
secdriven 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 secdriven 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 secdriven 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. secdriven on npm has been identified as a malicious package (versions 1.0.1, 1.0.7, 1.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004294IN-MAL-2026-004293IN-MAL-2026-004291IN-MAL-2026-004292

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks secdriven-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