Which versions of integrator-2829 are malicious?

Every published version of integrator-2829 on npm is considered malicious. Remove the package entirely.

How do I remediate integrator-2829 if I installed it?

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

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

Yes — integrator-2829 is associated with the GHSA-7f99-9p5f-5x2q 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 integrator-2829 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 integrator-2829 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging integrator-2829 across your stack and pipelines.

Malicious package

integrator-2829npm

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

MAL-2025-190506

Immediate action

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

npm uninstall integrator-2829

What this malware does

The package integrator-2829 was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

e38f5e4a7250f8d8199f26a59e70750071a304fc729893e38b7074a1cd3ab50b

a6bcecff983d9f430d14498333405f44d090846f460508f71de76679fb2076e9

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

Campaign

GHSA-7f99-9p5f-5x2q

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks integrator-2829-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