Which versions of ebpf-tracker-action are malicious?

The following npm versions of ebpf-tracker-action are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate ebpf-tracker-action if I installed it?

Remove ebpf-tracker-action 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 ebpf-tracker-action part of a known attack campaign?

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

Malicious package

ebpf-tracker-actionnpm

Malicious code in ebpf-tracker-action (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6077

Immediate action

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

npm uninstall ebpf-tracker-action

What this malware does

package.json declares preinstall: node index.js, which fires automatically on npm install. index.js collects hostname (os.hostname()), username (os.userInfo()), homedir, DNS servers, and package paths, reads /etc/passwd and /etc/hosts via fs.readFileSync, and HTTPS-POSTs the JSON payload to 66az91mywqmmbqau9k79bum1us0jo9cy.oastify.com (a Burp Collaborator subdomain). Package metadata (empty author, empty description, generic CI-flavored name ebpf-tracker-action) is consistent with a dependency-confusion attack targeting an internal package name. Any machine that installs this package leaks system identity and local account data to an attacker-controlled host at install time.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

f51f94366660f50b3ffaacedda1e956035ca8a7e5e0cadc33f2aefc20dd8a6a3

Frequently asked questions

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

Campaign

IN-MAL-2026-006942

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