Search This Blog

Powered by Blogger.

Blog Archive

Labels

Footer About

Footer About

Labels

Showing posts with label Organization Security. Show all posts

French Tax Data Theft: Threat Actors Steal Password and Remain Undetected


A threat actor used stolen passwords of employees at France’s tax admin to steal tax data on businesses and hundreds of thousands of taxpayers in June.

Agencies could not detect intrusion 

Neither France's national cybersecurity nor the tax administration could notice the data leaving. According to the agency ANSSI’s report, the attack worked because of weak login security, weak monitoring, and poorly separated networks.

DGFIP, the tax administration, handles France’s tax website impots.gouv.fr. The data came from a tool called E-Contact that taxpayers use to contact the tax administration.
According to the DGFIP, the stolen data includes slightly over 250,000 firms and slightly over 350,000 individuals. Passwords and internet accounts belonging to taxpayers were not hacked.

Attack tactic

For individuals, the data that may have been accessed or copied includes their tax ID, contact details, family circumstances, reference taxable income and tax withholding rate, and a summary of the messages they exchanged with the DGFIP. The messages themselves might have been intercepted by less than 250 individuals.
For companies, it includes the firm name, SIREN registration number, address and basic details of their messaging. 

Different routes used

The threat actor used two different routes, the first started with suspicious logins in May and resulted in E-Contact. 
The first route depended on various stolen passwords of DGFIP staff. The passwords were stolen by infostealers, malware that secretly saved login details, from systems the DGFIP did not handle, most probably from staff’s own systems.

The two portals that the threat actor exploited, ADER and PIGP, required only a password, so the stolen password worked. DGFIP staff use PIGP web portal for HR services and email. ADER offers access to a few DGFIP applications through the RIE, the network that links French government ministries. 

The threat actor reached the RIE via compromised Education ministry systems linked to it. Sensitive DGFIP apps were not taken out from the rest of the RIE, allowing threat actors to access them from parts of the network with no apparent need. Officials also discovered signs of various attempts to hack into other government entities on the network.

The attacker was able to access a lot of data even though the accounts they used had no special rights. ANSSI did not look at how user rights were managed for this report.
Data from the land registry was obtained via the second path. It passed through APEX, a portal for partners like land surveyors and notaries, which requested an email with a one-time code and a password.

Attackers Exploit CVE-2026-82329 to Forge JFrog Artifactory Admin Tokens



Cybersecurity researchers have observed attackers exploiting a critical JFrog Artifactory vulnerability shortly after its public disclosure. The flaw allows unauthenticated attackers to obtain administrative privileges on vulnerable self-hosted installations.

Tracked as CVE-2026-82329, the authentication-bypass vulnerability carries a CVSS severity score of 9.8. JFrog published its advisory and released security updates on August 28, 2026. Threat-intelligence researchers subsequently detected exploitation attempts beginning on September 1.

What Is JFrog Artifactory?

JFrog Artifactory is an artifact repository manager used by development teams to store, manage and distribute software packages and binary files.

Because Artifactory often connects directly to software-development and deployment pipelines, administrator-level access could allow attackers to manipulate repositories, steal credentials or introduce malicious components into software builds.

How CVE-2026-82329 Works

The vulnerability affects JFrog Access, the component responsible for authentication and credential management.

According to research shared by watchTowr, Artifactory installations without an additional join key configured may receive a fallback or “phantom” join key. Attackers can potentially abuse this condition to forge access and generate administrator-level authentication tokens.

Successful exploitation does not require an existing account or user interaction. An attacker only needs network access to a vulnerable Artifactory installation operating under the affected configuration.

The vulnerability does not directly provide remote-code execution. However, administrative control over an artifact repository could allow attackers to modify packages, create unauthorized accounts, access sensitive credentials and interfere with connected build systems.

Exploitation Detected in the Wild

WatchTowr researchers reported observing attackers use the vulnerability to generate administrator tokens and enumerate information about users, groups, credentials and federated-access configurations.

Some activity appeared limited to confirming whether a system was vulnerable. In a smaller number of cases, attackers reportedly created backdoor accounts and examined the compromised environment for opportunities to maintain access or expand the intrusion.

Researchers had not observed widespread scanning or mass exploitation when the activity was initially reported. Nevertheless, the rapid transition from public disclosure to exploitation demonstrates the limited time organizations have to secure internet-facing systems.

The Canadian Centre for Cyber Security has also warned that open-source reporting indicates active exploitation of CVE-2026-82329.

Patched JFrog Artifactory Versions

JFrog has released fixes across multiple supported Artifactory branches. Self-hosted customers should upgrade to the applicable fixed release:

  • 7.111.21

  • 7.117.28

  • 7.125.20

  • 7.133.29

  • 7.146.38

  • 7.161.20

JFrog says affected cloud environments have already been fortified and do not require customer action. Administrators of self-hosted deployments should consult the official JFrog security advisory to identify the correct update for their installation.

Recommended Security Measures

Organizations operating self-hosted JFrog Artifactory installations should:

  • Install the appropriate security update immediately.

  • Restrict internet access to Artifactory management interfaces.

  • Review audit logs for unexpected token or administrator-account creation.

  • Revoke unauthorized tokens and remove unfamiliar user accounts.

  • Rotate credentials and secrets accessible through the affected environment.

  • Inspect repositories for unauthorized package or configuration changes.

  • Examine connected CI/CD systems for evidence of lateral movement or artifact tampering.

CVE-2026-82329 is particularly dangerous because compromising a central artifact repository can affect more than the initially targeted server. Attackers with administrative access may be able to interfere with the software-development process and distribute modified components through trusted internal channels.

No public evidence currently confirms that CVE-2026-82329 is connected to the previously reported OpenAI and Hugging Face AI-agent activity involving an internal Artifactory environment. The two stories should be treated as separate security incidents.


Gen Threat Report Highlights H1 Global Threat Landscape


The Gen Threat Report is a twice-a-year analysis of the largest cyber threats impacting the digital threat landscape, providing a detailed insight into the trends impacting customers globally. The H1 report has provided some key insights. 

“The strongest pattern in the first half of 2026 was the way different threats converged around trust. Scams, account takeovers, malicious packages and AI agents all moved closer to the systems, workflows and permissions people already rely on,” said the report. 

46% of Gen threat findings were scams, whereas malvertising amounted for 30%. Gen stopped 114.2 million e-commerce scams and 20.3 million tech support scams.

These numbers are important, but they fit different kinds of scams into a few categories. A discovery does not reveal how the first trap became script execution, or how the script turned into a proxy change or browser, or how a wallet address was changed before the target verified a transaction.

Two important H1 findings

Two H1 investigations should be looked at in-depth. The first is a banking-malware campaign initiated with hacked corporate mailboxes and finished with browser manipulation and proxy. 

In the second finding, a cryptocurrency campaign deployed a Rust-based clipper and got C2 infrastructure pointers from Binance Smart Chain. 

The payloads are distinct, but none of the campaigns relied on breaking the genuine system at user end. The banking malware used a genuine account to set the trap whereas the clipper allowed the blockchain record an authentic transaction after modifying the local destination address.

Where did the business email come from

The banking campaign attacked users in Lithuania, Poland, Slovakia, and Czechia. The lures appeared to be genuine business emails such as invoice messages, scanned document verifications, and shipment notices. 

In various incidents, the texts were sent from hacked corporate mailboxes. The email was not designed to appear as if it came from an authentic organization. The emails were sent from an authentic account that threat actors had already hacked. 

DKIM and SPF can still sail through when a message is sent via genuine infrastructure, whereas reputation systems may spot a sender with an authentic history. 

The attachment deployed a JavaScript dropper, and then the chain travelled via PowerShell stages before reaching banking functionality and shellcode. The available signs indicate at GepyS.

The malware changed proxy settings and deployed a browser add-on, positioning itself nearby to the target’s banking session.

Malicious NPM Packages Attack Alibaba Users and Companies


Cybersecurity experts have found a new set of harmful npm packages that attack users of Alibaba developer tools via cross-platform RAT (Remote Access Trojan). This was part of an advanced, specific software supply chain attack against Chinese-speaking environments.

About the packages

Lib-mtop is an unscoped package with the same name as the private Alibaba package as @ali scope. Experts have not confirmed if this was due to the project developer going rogue or takeover of the maintainer account.

“Ch4ce,” the same maintainer account which presently redirects to a ‘not found’ error on npmjs[.]com also posted four other packages: local-config-parser, aone-kit-cli, aone-kit, and aone-sandbox. Three of these are empty wrappers carrying the same name as private, @ali-scoped packages, “which they declare as a dependency in the package.json file,” said Socket security researcher.

Attack tactic

The local-confi-parser package uses a genuine JSON configuration file parser, but shows dependencies that are posted from other npm user accounts. Together, they provide a channel for an advanced RAT attacking developers who may be working in organizations related with the Alibaba group.

Particularly, the infected loader functionality is divided and deployed into various packages sent to the victims. "When such a package is installed in an environment that has access to impersonated, scoped private packages, the dependency resolution works as expected, with a little extra functionality delivered through additional dependencies that get installed," Socket said.

Experts found 10 top-layer lure packages that depend on “smart-config-manager,” which works similar to a middle-layer bridge that links them to harmful payloads consisting of the loader logic. A low layer package continues to reach out to a GitHub repository to extract and store a rule engine configuration for use to run a malicious payload and contacts a remote server for fetching secondary malware.

What sets this attack apart?

A unique thing about the campaign is that the rule engine uses the vm module to implement the last phase and run the payload according to the target’s OS. The payload is fetched from a domain that mimics Alibaba to look natural and escape detection. 

The final payload is an advanced backdoor integrated with arbitrary file upload and download, comprehensive command execution, payload staging, lateral movement functions and host reconnaissance. The payload can also inject infected code into enterprise apps like Qoder, DingTalk, and Wukong.

"The goal of the campaign seems to be industrial espionage. While the number of downloads for the malicious packages is not significant, the impact of the campaign is hard to evaluate, because of the targeted nature and lateral-spread capabilities of the final-stage payload,” Socket said.