Which versions of ogd-analytics are malicious?

The following npm versions of ogd-analytics are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate ogd-analytics if I installed it?

Remove ogd-analytics 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 ogd-analytics part of a known attack campaign?

Yes — ogd-analytics is associated with the IN-MAL-2026-006875 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 ogd-analytics 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 ogd-analytics and packages like it before any post-install script runs.

Malicious package

ogd-analyticsnpm

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

MAL-2026-5987

Immediate action

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

npm uninstall ogd-analytics

What this malware does

package.json declares a preinstall lifecycle script that runs automatically during npm install. The script executes hostname, whoami, and pwd, then uses curl to POST the combined output (current user, host name, and install directory) as a urlencoded info field to https://webhook.site/1ea0386f-dcc0-4f1b-bdbb-61732d6535fb/ogd-analytics. webhook.site is an anonymous request-bin service, not a publisher-controlled domain, and the beacon has no relation to any advertised analytics functionality. The behavior is unconditional installer-side reconnaissance — user identity, machine identity, and filesystem location are exfiltrated to a third-party collector on every install, providing an attacker the host inventory needed for follow-on targeting (dependency confusion, internal-build-system fingerprinting).

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1df5f4bdd6e2f58ff581cbad0d01738b5f6464794ace1a9fa95eea061a5bb7d5

Frequently asked questions

No. ogd-analytics on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006875

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