Which versions of db-aggregator-api are malicious?

The following PyPI versions of db-aggregator-api are flagged malicious: 0.1.0, 0.2.0. Treat any of these as compromised.

How do I remediate db-aggregator-api if I installed it?

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

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

Yes — db-aggregator-api is associated with the 2025-11-db-aggregator-api 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 db-aggregator-api 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 db-aggregator-api (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging db-aggregator-api across your stack and pipelines.

Malicious package

db-aggregator-apiPyPI

Malicious code in db-aggregator-api (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191713

Immediate action

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

pip uninstall db-aggregator-api

What this malware does

Importing the module downloads and starts an infostealer.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-11-db-aggregator-api

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

2 flagged

0.1.00.2.0

Indicators of compromise (SHA-256)

27e7714dcae77ea7a597d423a9facccdcf9c7296afa5615094482df5d271708e

aed54ed734902c1a5749b7861e2ad95cc2d8c71c78fa4b0167499f9a1b296f9f

1fd9130301852bcd6a056ea866ea1ad14529dfb74363cf5da37132889d7bb2b9

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

Campaign

2025-11-db-aggregator-api

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks db-aggregator-api-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